Re: [Last-Call] Tsvart last call review of draft-ietf-idr-tunnel-encaps-19

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Joe and Brian:

 

As the replacement shepherd for draft-ietf-idr-tunnel-encaps-19.txt,  I am looking for the INT area statement on tunnels and MTU in tunnels.

 

Your intarea draft seems to have expired without any replacement.

 

Where is the latest set of comments on tunnels and MTU issue from INT area?

 

Sue

 

From: Joseph Touch [mailto:touch@xxxxxxxxxxxxxx]
Sent: Thursday, October 15, 2020 9:12 PM
To: Brian Trammell
Cc: tsv-art; Last Call; draft-ietf-idr-tunnel-encaps.all@xxxxxxxx; idr@xxxxxxxx
Subject: Re: [Last-Call] Tsvart last call review of draft-ietf-idr-tunnel-encaps-19

 

 



On Sep 28, 2020, at 11:32 PM, Brian Trammell via Datatracker <noreply@xxxxxxxx> wrote:

 

First and foremost, I was surprised to find no reference to tunnel or MTU 
anywhere in the document, especially given the guidance in section 6 to
stack tunnels. MTU issues are operationally difficulty in single-tunnel
environments and become more likely to cause problems in multiple-tunnel
environments. 

 

+1

 

This is discussed in detail, with some much more specific terminology, in draft-ietf-intarea-tunnels

 

In particular, *path MTU* is different from the received MTU, etc. It’s important to get this correct (note the many examples of current standards that do not).

 

Joe

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux