Re: [Idr] Working group last call for draft-ietf-idr-tunnel-encaps-04
"Acee Lindem (acee)" <acee@cisco.com> Fri, 26 May 2017 15:26 UTC
Return-Path: <acee@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D857129AAA; Fri, 26 May 2017 08:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 WBz6o2bSpmZd; Fri, 26 May 2017 08:26:20 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E506C129AD5; Fri, 26 May 2017 08:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4968; q=dns/txt; s=iport; t=1495812379; x=1497021979; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=a/UpPJmKAjaATUyBuaVHDH31xylF0LGelh7zl66+6ws=; b=eXbo8n+jU8/PMSz5DzvzEkc6XlpOTTqcarxxZfDlEXs1NdeoRZXEJ8EE qsQd7GxeVHoPqys7bfWu3vc6kYZwmBj12uO2dUDYnrdTPd/8UZxvr6ntb dzJVv2fcX/r0xGn+Sf+CdoxjgwOf8N//FUf5enNsN30mJRVaGyj2VRjsB Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AIAQAdSChZ/5pdJa1cGQEBAQEBAQEBAQEBBwEBAQEBg1VigQ0Hg2iKGJFllXmCDyENhXYCGoJwPxgBAgEBAQEBAQFrKIUZAQEBAwEBGwYROhsCAQgYAgIRFQICAiULFRACBAESiioQqzuCJotWAQEBAQEBAQEBAQEBAQEBAQEBAQEZBYELhzEBgxyEfSiCU4JgBZ4jAYcfjAiCBoU8ijWUTQEfOIEKdBVGhQgXgWN2AYd7gQ0BAQE
X-IronPort-AV: E=Sophos;i="5.38,397,1491264000"; d="scan'208";a="429024302"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 May 2017 15:26:19 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v4QFQIEX005191 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 26 May 2017 15:26:18 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 26 May 2017 11:26:18 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Fri, 26 May 2017 11:26:17 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Job Snijders <job@ntt.net>, "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-tunnel-encaps@ietf.org" <draft-ietf-idr-tunnel-encaps@ietf.org>
Thread-Topic: [Idr] Working group last call for draft-ietf-idr-tunnel-encaps-04
Thread-Index: AQHS0aHyfjzql++v8E6rbs0uznlaOqH/eQWAgAXjmgCAAWjtAA==
Date: Fri, 26 May 2017 15:26:17 +0000
Message-ID: <D54DC027.B154A%acee@cisco.com>
References: <2AEDAB02-02F4-46C2-92CA-8880BBAFAAAB@juniper.net> <213015a0-eb5f-3f17-f5f0-3aa864304a6d@labn.net> <20170525135424.3v3ea3rfdsquwizu@Vurt.local>
In-Reply-To: <20170525135424.3v3ea3rfdsquwizu@Vurt.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.196]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4B19B15FFF0C5E4BB1603DCB9688A657@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/o8OhbZHZdgdFNbmRpOY65vAhQRs>
Subject: Re: [Idr] Working group last call for draft-ietf-idr-tunnel-encaps-04
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 May 2017 15:26:33 -0000
Hi Job, Cisco is supporting Tunnel Attribute parsing and propagation as well as the TE-Policy tunnel type in an unreleased version of IOS-XR. The SR-TE Policy draft is https://www.ietf.org/id/draft-previdi-idr-segment-routing-te-policy-05.txt. Thanks, Acee On 5/25/17, 9:54 AM, "Idr on behalf of Job Snijders" <idr-bounces@ietf.org on behalf of job@ntt.net> wrote: >Dear all, > >TL;DR: I do not support advancing this document at this time. Lack of >full-spec implementation experience, and little feedback from actual >implementers, lead me to not support progression of this document. I >understand that this position has little to do with the actual contents >of the document. > >On Sun, May 21, 2017 at 03:58:29PM -0400, Lou Berger wrote: >> On 05/20/2017 03:47 PM, John G. Scudder wrote: >> > A working group last call has been requested for >> > draft-ietf-idr-tunnel-encaps-04. Please reply to the list with your >> > comments. As usual note we cannot advance the draft without >> > participation from the group. Please get your comments in before >> > June 5, 2017. >> >> - Since the question was raised on list: a partial implementation of >> this draft can be found in FRRouting, notably bgp_encap_tlv.{h,c} in >> https://github.com/FRRouting/frr/tree/master/bgpd . It supports: >> >> o encap attribute sent with other safis. The code uses it with the >> VPN safi to provide underlay tunnel information for VPN routes for >> NVO3 type applications. >> >> o "Remote Endpoint Address sub-TLV" for v4 and v6 >> >> o encode/decode of type specific and sub-TLV formats >> per draft -00 or -01 rev (this means it is a subset implementation. > >Cool stuff, thanks for sharing that! > >While John Scudder pointed out that there is no blocking requirement for >a document to have implementations before passing through WG LC. I (and >probably participants too) am of the opinion that actual feedback from >implementers is extremely valuable. > >Should an implementer find an actual technology issue, or lack of >clarity in the wording of the document, as long as the document in the >WG it'll be trivial to resolve any issues. I understand that there are >ways to modify a document after WG LC, but I think its simpler to be >able to say to the working group itself "this technology works, i have >an implementation". > >Should someone write a partial implementation, that might be a hint that >the document needs to be split up (or perhaps it is of no significance). >To properly assess a document, I hope for feedback from full >implementations (perhaps two technology components within a doc conflict >with each other). If parts of an Internet-Draft are not implemented by >anyone, I'd advocate the document should not (yet) progress further. > >With "implementation" i don't mean that you are shipping code to >customers, I'm fine with stuff hanging in private beta branches - all >I'm looking for is an attestation that the implementer found the >full specification implementable. RFC7942 is good guidance. > >I'd like to request the chairs to consider a slight adjustment of the >procedure: encourage the working group to create implementations >_before_ WGLC, so the working group can take implementer feedback into >account when assessing the proposed document. > >Kind regards, > >Job > >ps. if two full implementations show up during this WGLC, I will >ofcourse withdraw my non-support. > >_______________________________________________ >Idr mailing list >Idr@ietf.org >https://www.ietf.org/mailman/listinfo/idr
- [Idr] Working group last call for draft-ietf-idr-… John G. Scudder
- Re: [Idr] Working group last call for draft-ietf-… Job Snijders
- Re: [Idr] Working group last call for draft-ietf-… John G. Scudder
- Re: [Idr] Working group last call for draft-ietf-… Lou Berger
- Re: [Idr] Working group last call for draft-ietf-… Eric C Rosen
- Re: [Idr] Working group last call for draft-ietf-… Eric C Rosen
- Re: [Idr] Working group last call for draft-ietf-… Keyur Patel
- Re: [Idr] Working group last call for draft-ietf-… guntervandeveldecc
- Re: [Idr] Working group last call for draft-ietf-… Lou Berger
- Re: [Idr] Working group last call for draft-ietf-… Eric C Rosen
- Re: [Idr] Working group last call for draft-ietf-… Lou Berger
- [Idr] 答复: Working group last call for draft-ietf-… Xuxiaohu
- Re: [Idr] Working group last call for draft-ietf-… Job Snijders
- Re: [Idr] Working group last call for draft-ietf-… Eric C Rosen
- Re: [Idr] Working group last call for draft-ietf-… John E Drake
- Re: [Idr] Working group last call for draft-ietf-… Lou Berger
- Re: [Idr] Working group last call for draft-ietf-… Lou Berger
- Re: [Idr] Working group last call for draft-ietf-… Randy Bush
- Re: [Idr] Working group last call for draft-ietf-… Acee Lindem (acee)
- Re: [Idr] Working group last call for draft-ietf-… Eric C Rosen
- Re: [Idr] Working group last call for draft-ietf-… Job Snijders
- Re: [Idr] Working group last call for draft-ietf-… Acee Lindem (acee)
- Re: [Idr] Working group last call for draft-ietf-… Eric C Rosen
- Re: [Idr] Working group last call for draft-ietf-… Lou Berger
- Re: [Idr] 答复: Working group last call for draft-i… Eric C Rosen
- Re: [Idr] Working group last call for draft-ietf-… John E Drake
- Re: [Idr] Working group last call for draft-ietf-… Stefano Previdi (sprevidi)
- Re: [Idr] Working group last call for draft-ietf-… John G. Scudder
- Re: [Idr] Working group last call for draft-ietf-… Acee Lindem (acee)
- Re: [Idr] Working group last call for draft-ietf-… John Scudder
- Re: [Idr] Working group last call for draft-ietf-… John G. Scudder
- Re: [Idr] Working group last call for draft-ietf-… Eric C Rosen
- Re: [Idr] Working group last call for draft-ietf-… John G. Scudder
- Re: [Idr] Working group last call for draft-ietf-… Acee Lindem (acee)
- Re: [Idr] Working group last call for draft-ietf-… bruno.decraene
- Re: [Idr] Working group last call for draft-ietf-… bruno.decraene
- Re: [Idr] Working group last call for draft-ietf-… Eric C Rosen
- Re: [Idr] Working group last call for draft-ietf-… bruno.decraene
- Re: [Idr] Working group last call for draft-ietf-… bruno.decraene
- Re: [Idr] Working group last call for draft-ietf-… Eric C Rosen