Re: [Rtg-dt-encap-considerations] Proliferation of encapsulations ...
"Larry Kreeger (kreeger)" <kreeger@cisco.com> Thu, 21 May 2015 18:26 UTC
Return-Path: <kreeger@cisco.com>
X-Original-To: rtg-dt-encap-considerations@ietfa.amsl.com
Delivered-To: rtg-dt-encap-considerations@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0EFC1A1B22 for <rtg-dt-encap-considerations@ietfa.amsl.com>; Thu, 21 May 2015 11:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ff-o1UdulJ2Q for <rtg-dt-encap-considerations@ietfa.amsl.com>; Thu, 21 May 2015 11:26:19 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DFA11A1B21 for <Rtg-dt-encap-considerations@ietf.org>; Thu, 21 May 2015 11:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2378; q=dns/txt; s=iport; t=1432232779; x=1433442379; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=s2l2dAcF2XHt64JpdjJpqCyRVHm2U2aGKbV4clBhknk=; b=aDWOcGZpfW1jjuFzzigft1ToXgffktcA9gxp+fmYsThEziDyU/z1QA8v cXgW0S+1jRfZ3wSsTahm2X1z1C8jNZYBU4aHgoRqgq+LzI6Gh6Ow796lY YQI9AaG2KGXhkNsuoid75+UlX5xuTRHZsRJCMvhuFY2hwM153+Rdqz5bT A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ALBQDkIl5V/5FdJa1cgxBUXgbDFYFPCoV3AoFKORMBAQEBAQEBgQqEIwEBBAEBATc0GwIBCBgeECcLJQIEARKILA3SQgEBAQEBAQEBAQEBAQEBAQEBARYEizqFDIQtBYtNhy2LB5cdI4N4b4FGgQEBAQE
X-IronPort-AV: E=Sophos;i="5.13,470,1427760000"; d="scan'208";a="831186"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-2.cisco.com with ESMTP; 21 May 2015 18:25:54 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t4LIPsro007452 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 May 2015 18:25:54 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.6]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0195.001; Thu, 21 May 2015 13:25:53 -0500
From: "Larry Kreeger (kreeger)" <kreeger@cisco.com>
To: Erik Nordmark <nordmark@sonic.net>, "rtg-dt-encap-considerations@ietf.org" <Rtg-dt-encap-considerations@ietf.org>
Thread-Topic: [Rtg-dt-encap-considerations] Proliferation of encapsulations ...
Thread-Index: AQHQk+l9vo6VGMhkcU6Qfrp6Gv4Zs52GjFiAgACEpoD//4zJgA==
Date: Thu, 21 May 2015 18:25:53 +0000
Message-ID: <D1837032.148E92%kreeger@cisco.com>
References: <555E1212.5020300@sonic.net> <D183617A.148E77%kreeger@cisco.com> <555E2165.6070408@sonic.net>
In-Reply-To: <555E2165.6070408@sonic.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.9.150325
x-originating-ip: [10.24.15.85]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BAFA6786D27C73439ED20492CCEBE509@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-dt-encap-considerations/IxVifVp_3jLR_H_Svq4f4juDXFQ>
Subject: Re: [Rtg-dt-encap-considerations] Proliferation of encapsulations ...
X-BeenThere: rtg-dt-encap-considerations@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Design Team on Encapsulation Considerations discussion list <rtg-dt-encap-considerations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dt-encap-considerations>, <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/>
List-Post: <mailto:rtg-dt-encap-considerations@ietf.org>
List-Help: <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dt-encap-considerations>, <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 May 2015 18:26:21 -0000
The reason I was asking for examples was to understand whether it really was a separate encapsulation layer (e.g. GRE) versus just running directly over IP or Ethernet without and encapsulation (e.g. IP-in-IP). Since you named both, then further clarification in the text might be needed to cover both cases (direct encapsulation and encapsulation using an additional header). - Larry On 5/21/15 11:18 AM, "Erik Nordmark" <nordmark@sonic.net> wrote: >On 5/21/15 10:23 AM, Larry Kreeger (kreeger) wrote: >> Hi Erik, >> >> Where you wrote "where there might already exist an encapsulation over >>IP >> or Ethernet." do you think it would be useful to name a couple of >> examples? e.g. are you referring to GRE or something else? >GRE, but also IP-in-IP. >I'm a but concerned having examples in the document since it might be >interpreted as those proposals/proponents doing something wrong. Such as >misinterpretation would make it harder to do something cooperative down >the road. > > Erik > >> >> - Larry >> >> On 5/21/15 10:12 AM, "Erik Nordmark" <nordmark@sonic.net> wrote: >> >>> Based on our discussion I propose adding this text to the scope >>>section: >>> >>> "While the origin and focus of this document is the routing area and in >>> particular NVO3, SFC, and BIER, the considerations apply to other >>> encapsulations that are being defined in the IETF and elsewhere. There >>> seems to be an increase in the number of encapsulations being defined >>>to >>> run over UDP, where there might already exist an encapsulation over IP >>> or Ethernet. Feedback on how these considerations apply in those >>> contexts is welcome." >>> Comments? >>> >>> >>> Once that is in place and the document is out I'll send a note to the >>> IESG to raise awareness. >>> In that note I'll include any examples we have. Is there something >>>other >>> than draft-xu-softwire-ip-in-udp and draft-ietf-trill-over-ip that we >>> should use as examples? >>> >>> Based on how that goes I'll raise the "profileration of encapsulations" >>> with the IAB later. >>> >>> Thanks, >>> Erik >>> >>> >>> >>> _______________________________________________ >>> Rtg-dt-encap-considerations mailing list >>> Rtg-dt-encap-considerations@ietf.org >>> https://www.ietf.org/mailman/listinfo/rtg-dt-encap-considerations >> >
- [Rtg-dt-encap-considerations] Proliferation of en… Erik Nordmark
- Re: [Rtg-dt-encap-considerations] Proliferation o… Larry Kreeger (kreeger)
- Re: [Rtg-dt-encap-considerations] Proliferation o… Erik Nordmark
- Re: [Rtg-dt-encap-considerations] Proliferation o… Larry Kreeger (kreeger)
- Re: [Rtg-dt-encap-considerations] Proliferation o… Erik Nordmark
- Re: [Rtg-dt-encap-considerations] Proliferation o… Larry Kreeger (kreeger)