IETF Logo Mail Archive

Re: Next steps on Extension Header Insertion

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Tue, 08 November 2016 10:10 UTC

Return-Path: <sprevidi@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82C01129984 for <ipv6@ietfa.amsl.com>; Tue, 8 Nov 2016 02:10:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.018
X-Spam-Level:
X-Spam-Status: No, score=-16.018 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=-1.497, SPF_PASS=-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 E4wF1XPVU92C for <ipv6@ietfa.amsl.com>; Tue, 8 Nov 2016 02:10:03 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 188F7129675 for <ipv6@ietf.org>; Tue, 8 Nov 2016 02:10:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=599; q=dns/txt; s=iport; t=1478599802; x=1479809402; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=mHUHiVK5o4RFehh2AIuwZs1gAjTgu85VavvlWPV4qL8=; b=JVEiXIOJAqCggNHqrEW2Rmn4FEh+ZbVGpI7MJmL16q8LxoLDUyX1qdxe mEHx2qqJPLN/SsQFdZCxYdbeSrZ1HYlyqpobMSjCDqeBwnFdqzhGtj9LC I4EUOIbuwoePJpWDLtoJK/dejucRWd3L1NipleEoeKiw0uRCX/fLqEdOr 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CDAQA7oyFY/4kNJK1dGgEBAQECAQEBAQgBAQEBgy8BAQEBAR9YfweNMpcClFOCCB4LhXsCghI/FAECAQEBAQEBAWIdC4RhAQEBAwEBAQE3NAsFCwIBCBgeECcLJQIEDgWIVAgOtFiLSAEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhj6BfQiCUIRHgzGCLwEEiE+LfYViAZBGgViOPI0thAUBHjd6G4UPcoYugQwBAQE
X-IronPort-AV: E=Sophos;i="5.31,609,1473120000"; d="scan'208";a="171048332"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Nov 2016 10:10:02 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id uA8AA27F006215 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 8 Nov 2016 10:10:02 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 8 Nov 2016 05:10:01 -0500
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Tue, 8 Nov 2016 05:10:01 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: "otroan@employees.org" <otroan@employees.org>
Subject: Re: Next steps on Extension Header Insertion
Thread-Topic: Next steps on Extension Header Insertion
Thread-Index: AQHSOTB6lAiMBxGjIkCsW/LvP66R7g==
Date: Tue, 08 Nov 2016 10:10:01 +0000
Message-ID: <4E2C6B1A-ADD9-489D-8964-82D5C26E5ED8@cisco.com>
References: <B291E9E6-A803-423F-BFA5-87A74DCFB784@gmail.com> <dfe00826-1bcd-80ae-e6dc-7763c506cbe4@si6networks.com> <9CA73891-B4FA-47DF-82E1-A4867DBC6A3F@steffann.nl> <3C56AA77-18E4-4254-BB6A-A447CE115392@employees.org> <CAO42Z2zQ9ZVR8ih9CzY=3ytpLQJ9UCp37SM9N92cLpbfb4wyTQ@mail.gmail.com> <B5CA03B6-FB25-48F4-BF48-6F4C18A96DB4@employees.org> <63d048ed-63aa-e68a-f390-b6541d42e4ac@si6networks.com> <C63B5BB5-6F7F-405A-BC25-B1C48D58F286@cisco.com> <CAO42Z2w8oA3HXztTzBUFs7KWL4T9GPV_vWbP=m2r02JdPW_kiw@mail.gmail.com> <A8E70AF3-A132-4FAB-8F69-19D39B8E98B5@cisco.com> <12618a6b-b4a0-4254-391a-a6c3ab9367ab@gmail.com> <F6F6BD6B-73F8-4CB1-B3C2-CDA6908D13EA@employees.org>
In-Reply-To: <F6F6BD6B-73F8-4CB1-B3C2-CDA6908D13EA@employees.org>
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.61.192.1]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <60B73AEFF51D274286F8E0D726187B78@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/dbsnwaZmy1O47p1yLlz4Tf9PS-E>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2016 10:10:04 -0000

> On Nov 8, 2016, at 9:18 AM, otroan@employees.org wrote:
> 
>> So, the *fact* is that the current text is ambiguous, since it has been interpreted
>> both ways. As standards writers, we should hate ambiguity.
> 
> As standards writers, we should love interoperability.


agreed.

s.


> 
> Ole
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email