On Jun 12, 2012, at 2:22 PM, George, Wes wrote:

> 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.
> 

… i'd leave it that excercise to the implementer.
for internal APIs (ala "give me the rightmost AS") usually you operate on a 
normalized
representation of data and not the binary message stream. 

>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]] On Behalf Of
>> Murphy, Sandra
>> Sent: Friday, June 01, 2012 7:00 PM
>> To: [email protected]
>> 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
>> [email protected]
>> 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.
> _______________________________________________
> sidr mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/sidr

_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to