Hi Erik,

Thank you for your comments. New update addressing them will be available (v12) 
shortly

And more below.

Regards, 
Patrice Brissette 
Distinguished Engineer 
Cisco Systems 





On 2023-07-06, 02:44, "Erik Kline via Datatracker" <[email protected] 
<mailto:[email protected]>> wrote:


Erik Kline has entered the following ballot position for
draft-ietf-bess-evpn-virtual-eth-segment-11: No Objection


When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)




Please refer to 
https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
<https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/> 
for more information about how to handle DISCUSS and COMMENT positions.




The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-virtual-eth-segment/ 
<https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-virtual-eth-segment/>






----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


# Internet AD comments for draft-ietf-bess-evpn-virtual-eth-segment-11
CC @ekline


* comment syntax:
- https://github.com/mnot/ietf-comments/blob/main/format.md 
<https://github.com/mnot/ietf-comments/blob/main/format.md>


* "Handling Ballot Positions":
- https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
<https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/>


## Comments


* It's not clear to me why this isn't just Informational.

<PATRICE> Why do you think this draft should be informational? There are new 
mechanism being described in this document.


### S3.3


* I get that this functionality is highly desirable, but is there some loss
of interoperability among vendor equipment if it's not present? In other
words, why is this a MUST as opposed to SHOULD?


Seems like the alternative is that the switching among neighbor EVCs is
definitely less efficient, but could nevertheless be made to work.

<PATRICE> EVPN is about provide L2 reachability (intra-subnet communication). 
Connected access device/network sharing common subnet must have connectivity.

### S3.4


* These don't seem like "requirements" to me, just service descriptions.


### S3.5


* R5a does not seem like a requirement.

<PATRICE> What are you suggesting for these 2 comments? 








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

Reply via email to