Re: About ALL-ZERO-MAC's encapsulation in EVPN MAC/IP Advertisement route. //Re: Poll for adoption: draft-bonica-l3vpn-orf-covering-prefixes

["Ali Sajassi (sajassi)" <[e-mail]>]

On 7/2/14 6:41 AM, "Yakov Rekhter" <[e-mail]> wrote:

>Shunwan,
>
>> 
>> Dear all,
>> 
>> I have got into knots for presentment of ALL-ZERO-MAC's encapsulation
>> in EVPN MAC/IP Advertisement route.
>> 
>> draft-bonica-l3vpn-orf-covering-prefixes-03 defines the "Default MAC
>> Route ":
>> 
>>    o  Default MAC Route (DMR) - An EVPN MAC/IP Advertisement Route with
>>       MAC Address length equal to 0.
>> 
>> But draft-rabadan-l2vpn-dci-evpn-overlay-01 said:
>> 
>> 2.5.1 Use of the Unknown MAC route to reduce unknown flooding
>> 
>>       The solution suggested in this document is based on the use of an
>>       "Unknown MAC route" that is advertised by the Designated
>> Forwarder
>>       DC GW. The Unknown MAC route is a regular EVPN MAC/IP
>>       Advertisement route where the MAC Address Length is set to 48 and
>>       the MAC address to 00:00:00:00:00:00 (IP length is set to 0).
>> 
>> 
>> Can we use a uniform way?
>
>Yes, we'll update draft-bonica-l3vpn-orf-covering-prefixes to use
>00:00:00:00:00:00 MAC as the Default MAC Route.

Great! Since evpn draft only specifies MAC address w/ length 48.

Cheers,
Ali

>
>Yakov.
>
>> 
>> 
>> Regards,
>> Shunwan (Vincent)
>> 
>> -----邮件原件-----
>> 发件人: L3VPN [mailto:[e-mail]] 代表 Thomas Morin
>> 发送时间: 2014年6月27日 22:21
>> 收件人: [e-mail]
>> 抄送: [e-mail]
>> 主题: Poll for adoption: draft-bonica-l3vpn-orf-covering-prefixes
>> 
>> Hello working group,
>> 
>> This email starts a two-week poll on adopting
>> draft-bonica-l3vpn-orf-covering-prefixes-03 [1] as a working group
>> item.
>> 
>> Please send comments to the list and state if you support adoption or
>> not (in the later case, please also state the reasons).
>> 
>> This poll runs until July 12th.
>> 
>> 
>> *Coincidentally*, we are also polling for knowledge of any IPR that
>> applies to this draft, to ensure that IPR has been disclosed in
>> compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for
>> more details).
>> 
>> ==> *If you are listed as a document author or contributor* please
>> respond to this email and indicate whether or not you are aware of any
>> relevant IPR.
>> 
>> The draft will not be adopted until a response has been received from
>> each author and contributor.
>> 
>> If you are on the L3VPN WG mailing list but are not listed as an author
>> or contributor, then please explicitly respond only if you are aware of
>> any IPR that has not yet been disclosed in conformance with IETF rules.
>> 
>> Thank you,
>> 
>> Martin & Thomas
>> l3vpn chairs
>> 
>> [1] http://tools.ietf.org/html/draft-bonica-l3vpn-orf-covering-
>> prefixes-03
>