IETF Logo Mail Archive

Re: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>

"Darren Dukes (ddukes)" <ddukes@cisco.com> Mon, 03 June 2019 19:47 UTC

Return-Path: <ddukes@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 26DB2120811 for <ipv6@ietfa.amsl.com>; Mon, 3 Jun 2019 12:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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 header.b=aR4nW23K; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=QIDKW9bU
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 s4VWEYD1vCrP for <ipv6@ietfa.amsl.com>; Mon, 3 Jun 2019 12:47:01 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 640FE12004F for <ipv6@ietf.org>; Mon, 3 Jun 2019 12:47:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4480; q=dns/txt; s=iport; t=1559591221; x=1560800821; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=NVSyE0bnwNfIS8Y19T5doujHLhESbNHro7+etH8FX+8=; b=aR4nW23KkpSFjTTfdcxmJlpxF+uewz1DsgkBSbMj+X7U9nDJ1LhLzdpX QdXy3DkNhk/gQ9NtcS1EDL4RJzpIV41762BE7w4U+av1EqFUL461Uplm/ e//2ujIiXzUyj1FTVByaA/z4HTpSr576gzgWzE58sGfoyYiyoHLITzPCp c=;
IronPort-PHdr: 9a23:ZDhBWRPoblscjTE/fO0l6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEuKQ/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBj3IOPpYjcSF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BKAAAcePVc/5JdJa1mHAEBAQQBAQcEAQGBUQcBAQsBgT1QA2pVIAQLKAqECoNHA4RSiiOCV5cvgS6BJANUCQEBAQwBARgLCgIBAYRAAheCeyM0CQ4BAwEBBAEBAgEEbRwBC4VKAQEBAQIBAQEQCwYRDAEBLAsBBAsCAQgYAgIjAwICAiULFAEQAgQOBSKDAAGBagMODwECDJ4JAoE4iF9xgTGCeQEBBYJHgjsYgg8DBoEMKAGEbIZtF4FAP4ERJx+CTD6CYQEBA4FegwoygiaLUYJJmmMJAoINhj+McxQHgiKGcYwVgUaNAIcLjxMCBAIEBQIOAQEFgU84gVhwFRohKgGCQYIPDBeDTYUUhT4BcoEpjnoBgSABAQ
X-IronPort-AV: E=Sophos;i="5.60,547,1549929600"; d="scan'208";a="568903167"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 Jun 2019 19:46:57 +0000
Received: from XCH-ALN-010.cisco.com (xch-aln-010.cisco.com [173.36.7.20]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x53Jkv2X028768 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 3 Jun 2019 19:46:57 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-010.cisco.com (173.36.7.20) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 3 Jun 2019 14:46:57 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 3 Jun 2019 14:46:56 -0500
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 3 Jun 2019 15:46:56 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NVSyE0bnwNfIS8Y19T5doujHLhESbNHro7+etH8FX+8=; b=QIDKW9bUP8dosnOKTwJeTvhsHpYk4EYAtDb+Xr5bfKDQIr9UMqqetVXj2/j2KMskhIN2a/MVgDyqfskH64MfO1J15UwQdVJU78Tn+RqKJZEGPVBGjDzy8HGJAWIhyfwjHqL/ckfp8onWptU0WF4wHMfcZyGaBhaeU/NfZ9WSu4c=
Received: from DM6PR11MB3516.namprd11.prod.outlook.com (20.177.220.141) by DM6PR11MB3098.namprd11.prod.outlook.com (20.177.219.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.22; Mon, 3 Jun 2019 19:46:55 +0000
Received: from DM6PR11MB3516.namprd11.prod.outlook.com ([fe80::d59f:9fbe:1f8b:bac7]) by DM6PR11MB3516.namprd11.prod.outlook.com ([fe80::d59f:9fbe:1f8b:bac7%7]) with mapi id 15.20.1943.018; Mon, 3 Jun 2019 19:46:55 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
CC: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>
Thread-Topic: 6man w.g. last call for <draft-ietf-6man-segment-routing-header-19.txt>
Thread-Index: AQHVEKPvir/m07qyXEqVGUt8jQpJGaZ+tJAAgAu0V4A=
Date: Mon, 03 Jun 2019 19:46:55 +0000
Message-ID: <ECE11EF9-6CC0-4EBE-98D3-AD5E7E5B782A@cisco.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <588C586F-C303-418E-8D26-477C4B37CF92@gmail.com> <787AE7BB302AE849A7480A190F8B93302EA8F6B2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302EA8F6B2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ddukes@cisco.com;
x-originating-ip: [161.44.192.68]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 93cd2110-6af0-4ff4-6d20-08d6e85c3b88
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:DM6PR11MB3098;
x-ms-traffictypediagnostic: DM6PR11MB3098:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <DM6PR11MB30984BA3BF149B17382E0BAAC8140@DM6PR11MB3098.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0057EE387C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(396003)(366004)(136003)(39860400002)(189003)(199004)(229853002)(99286004)(26005)(81156014)(76116006)(2501003)(305945005)(91956017)(186003)(54906003)(86362001)(478600001)(256004)(8936002)(8676002)(76176011)(2351001)(81166006)(64756008)(66446008)(66556008)(476003)(6512007)(53546011)(6486002)(6506007)(486006)(66946007)(446003)(66476007)(11346002)(2616005)(73956011)(5640700003)(102836004)(7736002)(6916009)(6436002)(6306002)(4743002)(3846002)(53936002)(6246003)(6116002)(2906002)(4326008)(36756003)(5660300002)(25786009)(316002)(82746002)(66066001)(83716004)(14454004)(71200400001)(966005)(68736007)(71190400001)(33656002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB3098; H:DM6PR11MB3516.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: cF1iNFGS+mVeF40MlpN+0lGCc8BEAb5cXdYz8rLDyagibt9FoT7u8g5CVjbB1jQ/dw1VN3mrW8ejTk/IK1k2y5Ok1JG4CB3I4bSwGPTgTXJK5ZkOn4f2hHqQtYVQhjdmsC1QL1UQ3xRqDwRCwm2iHXAv2u3HE/3iuefDK9a4diWCuMaPMnq4fPL1EaF70OQiBR3xT3cyUsd1Q8t0eV99WrApd5MMuZjEkRW9pTpVOf7gUY1Toa8o5Hqph4/pJlp/T4PGGJcGHdgf731e1Ff30DJmpFLwmIXz+8U1ji2ogg5TNc3rXBPdiHBPnk7oQo2EQvvH8VNnJUZCPh8/fUoG9TZTNxAnBl/yv9wTwH0ZMUsFWKk1dbCIaAvDeYoynfxicqWgm2+LtEBoPA6Br2tuIeT6OHvQAU+d02M0srgkphw=
Content-Type: text/plain; charset="utf-8"
Content-ID: <B26A1D91E7C0A149861115F794A86BD5@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 93cd2110-6af0-4ff4-6d20-08d6e85c3b88
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jun 2019 19:46:55.2266 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ddukes@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3098
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.20, xch-aln-010.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SlgzIfd51hD2M6I-4FF7t2PwbeY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 03 Jun 2019 19:47:04 -0000

Hi Med, this was closed by the WG during the previous last call, concluding with this text.

Darren

> On May 27, 2019, at 5:02 AM, mohamed.boucadair@orange.com wrote:
> 
> Hi Bob, all,
> 
> I do still don't understand the intent of this field:  
> 
>   o  Tag: tag a packet as part of a class or group of packets, e.g.,
>      packets sharing the same set of properties.  When tag is not used
>      at source it MUST be set to zero on transmission.  When tag is not
>      used during SRH Processing it SHOULD be ignored.  Tag is not used
>      when processing the SID defined in Section 4.3.1.  It may be used
>      when processing other SID types which are not defined in this
>      document.  The allocation and use of tag is outside the scope of
>      this document.
> 
> In the absence of a clear definition of this field, it is better to set these bits as unassigned. 
> 
> Cheers,
> Med
> 
>> -----Message d'origine-----
>> De : ipv6 [mailto:ipv6-bounces@ietf.org] De la part de Bob Hinden
>> Envoyé : mercredi 22 mai 2019 15:40
>> À : IPv6 List
>> Cc : Bob Hinden
>> Objet : 6man w.g. last call for <draft-ietf-6man-segment-routing-header-
>> 19.txt>
>> 
>> Hello,
>> 
>> This message starts a new two week 6MAN Working Group Last Call on
>> advancing:
>> 
>>       Title           : IPv6 Segment Routing Header (SRH)
>>       Authors         : Clarence Filsfils
>>                         Darren Dukes
>>                         Stefano Previdi
>>                         John Leddy
>>                         Satoru Matsushima
>>                         Daniel Voyer
>> 	Filename        : draft-ietf-6man-segment-routing-header-19.txt
>> 	Pages           : 32
>> 	Date            : 2019-05-21
>> 
>>    https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header
>> 
>> as a Proposed Standard.
>> 
>> This document was in an extended last call that started in March of 2018.
>> An issue tracker was set up, and eight new versions of the draft were
>> produced and discussed on the list and at face to face 6man sessions.
>> All of the issues in the tracker have been closed.  The chairs believe it
>> is ready to advance, but given the number of changes and the time that
>> elapsed, a new w.g. last call is warranted.  Please review the new
>> document.
>> 
>> Our thanks to the authors/editors and the working group for the work on
>> this document.
>> 
>> Substantive comments and statements of support for publishing this
>> document should be directed to the mailing list. Editorial suggestions can
>> be sent to the author.  This last call will
>> end on 5 June 2019.
>> 
>> Thanks,
>> Bob & Ole
>> 
>> 
>> 
>> 
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> 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