Re: [spring] Working Group Adoption Call for draft-filsfils-spring-srv6-network-programming

"Darren Dukes (ddukes)" <ddukes@cisco.com> Wed, 20 March 2019 17:57 UTC

Return-Path: <ddukes@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA3E7126C87; Wed, 20 Mar 2019 10:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 header.b=mwJf6TWf; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Mnxxf5+s
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 saPocakoxwtP; Wed, 20 Mar 2019 10:57:18 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD514129508; Wed, 20 Mar 2019 10:57:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12305; q=dns/txt; s=iport; t=1553104635; x=1554314235; h=from:to:cc:subject:date:message-id:mime-version; bh=ZVJLCZS3HnnxEV4dJTn/XaZIYv27k5hleX8u1wylQxY=; b=mwJf6TWfmophghzUZRWV71iqMwdb2lDYFqmyE7y/62AKac8KfklTp8rf g8PRfKJLq7FeKmM5yiIva6YWn4u6kz7I5YCKE2Rm8Omxhi3phkVeEgVZX Sg7SLW/9Rszhuqw0NFuJhiG2J73U7z8jMbxlKF8B5srIQidrGwKFfJOdx c=;
IronPort-PHdr: 9a23:ejaEmRRsLl0bu56R7Ib0/mAuMtpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESUDNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOiA2AcdPT3du/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A9AACjfZJc/4MNJK1lHAEBAQQBAQcEAQGBUgYBAQsBgQ4vUANodAQLJwqEA4NHA48mgleSPoRJgS6BJANUCwEBLIRAGYRQIjUIDQEBAwEBCQEDAm0cDIVLBh0GChMBATcBEQEIFSoDAgQwFBMEDgWDIgGBEUwDFQECoAgCihRxgS+CeAEBBYUJGIIMCIEvAYoSgR8XgUA/JoESH4FOfogLMYImjGmEGodAjDwJApMuGZNlniACBAIEBQIOAQEFgU4CNIFWcBVlAYJBggo2gziKU3KBKIpFAYEeAQE
X-IronPort-AV: E=Sophos;i="5.60,249,1549929600"; d="scan'208,217";a="248411444"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 20 Mar 2019 17:57:13 +0000
Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x2KHvD0U029359 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 20 Mar 2019 17:57:13 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 20 Mar 2019 12:57:12 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 20 Mar 2019 13:57:11 -0400
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 20 Mar 2019 12:57:11 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZVJLCZS3HnnxEV4dJTn/XaZIYv27k5hleX8u1wylQxY=; b=Mnxxf5+sSevbW1PvSDzOsaK1/xrOCkzpIHOIqWMdzU9K32vu57EJNJlcd0qW/fQfRvJXSIxsvmU5WW4/RAigTCQ3x/YrtM7rU0qmWJAvQbOtUN8L3d3uJTAjVd/6Evhw03U75jWGaE6Xq9DjWUFwhtZcfI6eFFumOichKi4oCcg=
Received: from BL0PR11MB3505.namprd11.prod.outlook.com (20.177.205.209) by BL0PR11MB2978.namprd11.prod.outlook.com (20.177.147.212) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1730.15; Wed, 20 Mar 2019 17:57:09 +0000
Received: from BL0PR11MB3505.namprd11.prod.outlook.com ([fe80::990:c805:c005:b3bd]) by BL0PR11MB3505.namprd11.prod.outlook.com ([fe80::990:c805:c005:b3bd%4]) with mapi id 15.20.1730.013; Wed, 20 Mar 2019 17:57:09 +0000
From: "Darren Dukes (ddukes)" <ddukes@cisco.com>
To: Adrian Farrel <adrian@olddog.co.uk>
CC: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, SPRING WG <spring@ietf.org>, "draft-filsfils-spring-srv6-network-programming@ietf.org" <draft-filsfils-spring-srv6-network-programming@ietf.org>
Thread-Topic: [spring] Working Group Adoption Call for draft-filsfils-spring-srv6-network-programming
Thread-Index: AQHU30ZWferRtv2fvUWaAS3Zgr4FQA==
Date: Wed, 20 Mar 2019 17:57:09 +0000
Message-ID: <115EF2F7-D92E-4B54-B9D2-B3EB17EF70E9@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.16.1.190220
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ddukes@cisco.com;
x-originating-ip: [161.44.192.53]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f9594e5d-333e-49c0-1b32-08d6ad5d7956
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:BL0PR11MB2978;
x-ms-traffictypediagnostic: BL0PR11MB2978:
x-microsoft-antispam-prvs: <BL0PR11MB2978AE290F2A3971386ABF6EC8410@BL0PR11MB2978.namprd11.prod.outlook.com>
x-forefront-prvs: 098291215C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(39860400002)(346002)(396003)(136003)(366004)(199004)(189003)(2906002)(58126008)(6246003)(54906003)(316002)(25786009)(14454004)(99286004)(102836004)(4326008)(6506007)(26005)(86362001)(68736007)(81166006)(8676002)(82746002)(6916009)(81156014)(53936002)(7736002)(6512007)(54896002)(6306002)(36756003)(6436002)(478600001)(33656002)(8936002)(229853002)(6486002)(5024004)(256004)(3846002)(71190400001)(790700001)(6116002)(5660300002)(97736004)(106356001)(476003)(2616005)(105586002)(186003)(83716004)(66066001)(71200400001)(486006); DIR:OUT; SFP:1101; SCL:1; SRVR:BL0PR11MB2978; H:BL0PR11MB3505.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: VVnezR1PHTGvZi831QUSH1PZt48RMyuUXR5OIB7yilfVj5V1J15mzmPgBnBMJMN57vtLS8anhyq1mx6pV8pqZbY+nYCOz1TVgAFQ0b2H4lV2cBw9q62BJ97JZgpJW+ZiqIxlIrrZgsyNMZ1C/UiOiuwEk5AT+CiyE0vFbYz4ASGRlDcuQuHS0lNI/CUk7u1NwRRHgk2tupxkqQjeGSnrpLt5BBIg6eNyRBj1JVXOKKzmk57GmGWVvmf9G6SBw/JOiSElbThwTN99BP0xutTyhxeGzpZ3QF6E88VFeP+hUzQlkZTuuWOMOKUS5GdQvo2ZhQADfgOZreDX6BD3BM6vo5viLXpiJ4lCQY2TnIydgwkYL0E7nQRj7VsNHL7oWbEUtafrOljyR5bJ302FPD4rf6qLxxZREd2CO1JZQNFmbgA=
Content-Type: multipart/alternative; boundary="_000_115EF2F7D92E4B54B9D2B3EB17EF70E9ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f9594e5d-333e-49c0-1b32-08d6ad5d7956
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2019 17:57:09.7783 (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-Transport-CrossTenantHeadersStamped: BL0PR11MB2978
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.20, xch-rcd-010.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/iMgVtB5Vc5jHfuKKgOm1lLvCpJo>
Subject: Re: [spring] Working Group Adoption Call for draft-filsfils-spring-srv6-network-programming
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2019 17:57:21 -0000

Hi Adrian.



The draft-6man-segment-routing-header has already defined the processing of a segment.  And this document, as it evolves as a WG document, should follow that processing.



Darren







From: spring <mailto:spring-bounces@ietf.org> on behalf of "mailto:adrian@olddog.co.uk" <mailto:adrian@olddog.co.uk>



Thanks for this poll, Bruno,



Before taking up work on this draft, would it be worth working with 6man to check that the repurposing of IPv6 addresses would be unlikely to cause a great fight? It would probably be better to not have two WGs fighting.



And, in case someone is confused by my comments, RFC 4291 has…



   IPv6 addresses are 128-bit identifiers for interfaces and sets of

   interfaces (where "interface" is as defined in Section 2 of [IPV6]).



And RFC 8200 has…



      interface    a node's attachment to a link.



and



      Destination Address 128-bit address of the intended recipient of

                          the packet (possibly not the ultimate

                          recipient, if a Routing header is present).

                          See [RFC4291] and Section 4.4.



Now, it is possible that everyone will say “Yeah, go ahead.” Or they may say, “You can only do this if you’re also updating 4291 and 8200.” Or, of course, they may also say, “Whoa, it would be a really big step to address a function or an instruction or something other than an interface, notwithstanding that they are routable.”



I’m not prejudging what answer we might get, but think it would be worth asking.



Best,

Adrian