Re: [sidr] WGLC for draft-ietf-sidr-pfx-validate-06

Speaking as regular ol' member:

wrt:

>One nit - we've had several conversations about whether to use 
>AS_Path as synonymous with AS4_Path since we require (with a 
>MUST) support for 4-octet ASNs. I don't remember which way 
>we came down on the matter, whether to explicitly say 
>AS4_PATH since that is what will really be used, or to leave 
>that as an exercise for the implementer.

I do not believe that AS4_PATH would "really be used" by a bgpsec capable router.

The MUST support for 4 byte AS numbers means that the following text from RFC4893 applies:

   The new attributes, AS4_PATH and AS4_AGGREGATOR SHOULD NOT be carried
   in the UPDATE messages between NEW BGP peers.  A NEW BGP speaker that
   receives the AS4_PATH and AS4_AGGREGATOR path attributes in an UPDATE
   message from a NEW BGP speaker SHOULD discard these path attributes
   and continue processing the UPDATE message.

Each neighbor that has negotiated the bgpsec capability  is a "NEW BGP speaker" because it must support 4 byte ASNs.  NEW BGP speakers use 4 byte ASNs in the AS_PATH (not AS4_PATH).

The RFC4893 text says SHOULD rather than MUST, so it is possible that a bgpsec speaker might actually receive the AS4_PATH attribute, but dropping the attribute is expected and just fine.

--Sandy, speaking as regular ol' wg member

________________________________________
From: George, Wes [wesley.george@twcable.com]
Sent: Tuesday, June 12, 2012 8:22 AM
To: Murphy, Sandra; sidr@ietf.org
Subject: RE: WGLC for draft-ietf-sidr-pfx-validate-06

I have read this draft and previous versions and I support publishing it.

One nit - we've had several conversations about whether to use AS_Path as synonymous with AS4_Path since we require (with a MUST) support for 4-octet ASNs. I don't remember which way we came down on the matter, whether to explicitly say AS4_PATH since that is what will really be used, or to leave that as an exercise for the implementer.

Thanks,

Wes George

> -----Original Message-----
> From: sidr-bounces@ietf.org [mailto:sidr-bounces@ietf.org] On Behalf Of
> Murphy, Sandra
> Sent: Friday, June 01, 2012 7:00 PM
> To: sidr@ietf.org
> Subject: [sidr] WGLC for draft-ietf-sidr-pfx-validate-06
>
> The authors have stated that they believe that draft-ietf-sidr-pfx-
> validate-06 "BGP Prefix Origin Validation" is ready for a working group
> last call.
>
> The draft can be accessed at http://tools.ietf.org/html/draft-ietf-sidr-
> pfx-validate-06 and https://datatracker.ietf.org/doc/draft-ietf-sidr-
> pfx-validate/
>
> This announces the beginning of the wglc.  The last call will end on
> Friday, 15 Jun 2012.
>
> Please judge whether you believe that this work is ready for publication
> and send any comments to the list.
>
> --Sandy, speaking as wg co-chair
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.