Re: [Idr] WG adoption ofdraft-dhrao-idr-4octet-extcomm-generic-subtype

["Dhananjaya Rao (dhrao)" <[e-mail]>]

 
Hi Bruno,

>-----Original Message-----
>From: [e-mail] [mailto:[e-mail]] On 
>Behalf Of [e-mail]
>Sent: Tuesday, November 25, 2008 12:45 AM
>To: [e-mail]; [e-mail]
>Subject: Re: [Idr] WG adoption 
>ofdraft-dhrao-idr-4octet-extcomm-generic-subtype
>
>Support.
>

Thanks for your support.

>
>In section 3 (Deployment Considerations)
>
>> A speaker with a 4-octet Autonomous System may have a customer or
>> peer with a 2-octet Autonomous System.  If such a peer supports
>> 4-octet extended communities, then it will be able to tag its routes
>> with the 4-octet extended community defined by the speaker.  If the
>> peer does not support 4-octet extended communities, then the speaker
>> may need to define an appropriate standard community value for the
>> same purpose.
>
>Could the document explicitly states whether the reserved 
>AS_TRANS value (ASN 23456 defined in RFC 4893) can (or cannot) 
>be used by a non compliant 2-octet AS peering with a 4-octet AS?
>

Yes, AS_TRANS can be used for the above stated purpose. As discussed,
we will add this to the draft as one example of an appropriate 
standard community.

Regards,
-Dhananjaya

>Thanks,
>Regards,
>Bruno
>
>> -----Message d'origine-----
>> De : [e-mail] [mailto:[e-mail]] De 
>la part de Yakov Rekhter
>> Envoyé : dimanche 2 novembre 2008 16:27
>> À : [e-mail]
>> Objet : [Idr] WG adoption of 
>draft-dhrao-idr-4octet-extcomm-generic-subtype
>> 
>> Folks,
>> 
>> Please send your comments on the attached. The deadline for comments
>> is Nov 17, 2008.
>> 
>> Yakov.
>> ------- Forwarded Message
>> 
>> Date:    Fri, 31 Oct 2008 18:29:47 -0400
>> From:    Jeffrey Haas <[e-mail]>
>> To:      [e-mail]
>> Subject: [Idr] WG adoption of 
>draft-dhrao-idr-4octet-extcomm-generic-subtype
>> 
>> Yakov and Sue,
>> 
>> We'd like to request the working group adopt the internet-draft
>> draft-dhrao-idr-4octet-extcomm-generic-subtype as a working 
>group item.
>> This draft adds a generic 4 octet extended community to 
>complement the
>> 2-octet AS community behavior publised in RFC 1997.
>> 
>> Although very similar to 
>draft-ietf-l3vpn-as4octet-ext-community, we'd
>> like to request adoption of this draft in IDR since it has no l3vpn
>> specific semantics.
>> 
>> - -- Jeff
>> _______________________________________________
>> Idr mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/idr
>> 
>> ------- End of Forwarded Message
>> 
>> _______________________________________________
>> Idr mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/idr
>_______________________________________________
>Idr mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/idr
>
_______________________________________________
Idr mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/idr