Spencer Dawkins has entered the following ballot position for
draft-ietf-nvo3-arch-07: 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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-nvo3-arch/



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

I found a small number of nits that I couldn't error-correct while
reading, but I'm especially interested in Suresh's Discuss on TTL
decrementing.

I couldn't parse 

   L3 VN to Legacy L2:  This type of gateway forwards packets on between
         L3 VNs and legacy L2 networks such as VLANs or L2 VPNs.  The
         MAC address in any frames forwarded between the legacy L2
                                             ^^^^^^^^^^^^^^^^^^^^^
         network would be the MAC address of the gateway.
         ^^^^^^^
         
I could guess, but something is borked, and I'm not sure what is meant.

I'm having the same problem with 

   L3 VN to L2 VN:  This type of gateway forwards packets on between L3
         VNs and L2 VNs.  The MAC address in any frames forwarded
         between the L2 VN would be the MAC address of the gateway.
         ^^^^^^^^^^^^^^^^^
         
further down.

I know what "hard" and "soft" errors are in my world, but I'm not sure
what's meant here. 

   o  Delivered to correct NVE, but could not deliver packet to TS-X
      (soft error).

   o  Delivered to correct NVE, but could not deliver packet to TS-X
      (hard error).
      
Are these clearly understood terms of art in NV03? If not, could you
provide some parenthetical "i.e.", as you do for other items in the same
list, or some reference if an appropriate reference exists?

Is

   o  Allow different protocols and architectures to be used to for
                                                             ^^ ^^^
      intra- vs. inter-NVA communication.  
      
just a typo, or is there something missing between "to" and "for"?


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

Reply via email to