1 / 8

SPPP Protocol

SPPP Protocol. Session Peering Provisioning Protocol draft-ietf-drinks-spprov-01. Progress. Route Offer/Accept Operations Egress Route Operations More Succinct LUF and LRF Support Abstracted Route Record Types Abstracted Public Identifier Type Carrier of Record Claim

hector
Download Presentation

SPPP Protocol

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SPPP Protocol Session Peering Provisioning Protocol draft-ietf-drinks-spprov-01

  2. Progress Route Offer/Accept Operations Egress Route Operations More Succinct LUF and LRF Support Abstracted Route Record Types Abstracted Public Identifier Type Carrier of Record Claim Progressed with corresponding updates to Protocol Spec Document

  3. Route Group Offer/Accept • Both terminating and dependent peering organizations have ability to control which Route Group SED is included in query response for a given Public Identifier. • Routes are offered by terminating peer. • Routes are accepted or rejected by dependent peer. • Once Route is accepted, it’s SED may be included in subsequent resolution responses.

  4. Route Group Offer/Accept • Operations • addRteGrpOffersRqst • getRteGrpOffersRqst • delRteGrpOffersRqst • acceptRteGrpOffersRqst • rejectRteGrpOffersRqst

  5. Route Group Offer/Accept <complexType name="RteGrpOfferType"> <sequence> <element name="base" type="spppb:BasicObjType"/> <element name="rteGrpOfferKey" type="spppb:RteGrpOfferKeyType"/> <element name="status" type="spppb:RteGrpOfferStatusType"/> <element name="offerDateTime" type="dateTime"/> <element name="acceptDateTime" type="dateTime" minOccurs="0"/> <element name="ext" type="spppb:ExtAnyType" minOccurs="0"/> </sequence> </complexType> <complexType name="RteGrpOfferKeyType"> <sequence> <element name="rteGrpKey" type="spppb:ObjKeyType"/> <element name="offeredTo" type="spppb:OrgIdType"/> </sequence> </complexType> <simpleType name="RteGrpOfferStatusType"> <restriction base="token"> <enumeration value="offered"/> <enumeration value="accepted"/> </restriction> </simpleType>

  6. Carrier of Record Claim • Registrant provisioning a TN is able to optionally claim that is it, or will be, the Carrier of Record for that TN. This allows registry policies to give preference to COR routes over transit routes. • TNs having COR claim may only be matched against resolution queries if the COR claim has been verified/approved by the registry, according to the policies of that registry. However, this is a matter of policy. Other policies may be appropriate. • Registrant can provision TN COR claims “ahead of time” allowing the registry to, at some future time or date, “discover” that the claim has become valid.

  7. Carrier of Record Claim <element name="addPubIdsRqst" type="spppb:AddPubIdsRqstType"/> <complexType name="TNType"> <extension base="spppb:PubIdType"> <sequence> <element name="tn" type="string"/> <element name="corClaim" type="spppb:CORInfoType" minOccurs="0"/> </sequence> </extension> </complexType> <complexType name="CORInfoType"> <sequence> <element name="corClaim" type="boolean" default="true"/> <element name="corClaimStatus" type="boolean" minOccurs="0"/> <element name="corClaimStatusDate" type="dateTime" minOccurs="0"/> </sequence> </complexType>

  8. Next Steps • Finalize a remaining aspects of the protocol, e.g. • COR Indication • File Based Provisioning • Possible Prioritization Across Peers • Finalize the document • Update sections to adhere to several detailed review comments and to get in sync with XSD, etc. • Some re-organization of sections. • Add in remaining operation descriptions (add destination group, del). • Finalize descriptions of the common/base protocol data structures and concepts such as BaseRqstType, BaseRspnsType, authorization, organization ID scheme, transaction handling. • Final prototype implementation

More Related