[Softwires] softwire-encaps-safi
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Softwires] softwire-encaps-safi
- To: David Ward <dward at cisco.com>
- Subject: [Softwires] softwire-encaps-safi
- From: Carlos Pignataro <cpignata at cisco.com>
- Date: Sat, 24 May 2008 00:07:50 -0400
- Cc: "Francois Le Faucheur IMAP <flefauch at cisco.com>" <flefauch at cisco.com>, Alain Durand <Alain_Durand at cable.comcast.com>, Jari Arkko <jari.arkko at piuha.net>, softwires at ietf.org, "John G. Scudder <jgs at juniper.net>" <jgs at juniper.net>, jianping <jianping at cernet.edu.cn>, "Russ White <riw at cisco.com>" <riw at cisco.com>
- Delivered-to: ietfarch-softwires-web-archive at core3.amsl.com
- Delivered-to: softwires at core3.amsl.com
- In-reply-to: <89F15385-FDFE-4973-A8B2-A2F358655DFE@cisco.com>
- List-archive: <http://www.ietf.org/pipermail/softwires>
- List-help: <mailto:softwires-request@ietf.org?subject=help>
- List-id: softwires wg discussion list <softwires.ietf.org>
- List-post: <mailto:softwires@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
- Organization: cisco Systems, Inc.
- References: <89F15385-FDFE-4973-A8B2-A2F358655DFE@cisco.com>
- Sender: softwires-bounces at ietf.org
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080421 Thunderbird/2.0.0.14 Mnenhy/0.7.5.0
On 5/5/2008 David Ward <dward at cisco.com> wrote:
> draft-ietf-softwire-encaps-safi-00.txt
Please find some comments on ietf-softwire-encaps-safi, I hope these are
useful:
Tunnel Type (2 octets): It identifies the type of the tunneling
technology being signaled. This document defines the following types:
- L2TPv3: Tunnel Type = 1
L2TPv3 can be encapsulated in different ways over IP (e.g., directly
over IP proto 115, and over UDP). This document refers implicitly
(without mention) to L2TPv3 over IP (the only L2TPv3 mandatory
encapsulation from RFC3931), but does not explicitly clarify it. Could
this be disambiguated, e.g., by either: i. Renaming the Tunnel Type 1 to
"L2TPv3 over IP", or ii. Providing further L2TPv3 encap details (IP vs.
UDP, etc) in the Encapsulation sub-TLV for the L2TPv3 TLV Type?
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.