Re: [spring] I-D Action: draft-ietf-spring-segment-routing-policy-06.txt

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Mon, 16 December 2019 10:07 UTC

Return-Path: <ketant@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 2B98112013A for <spring@ietfa.amsl.com>; Mon, 16 Dec 2019 02:07:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.498
X-Spam-Level:
X-Spam-Status: No, score=-14.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=GWiAHWng; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=al5qALtA
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 G1lTTmEfvm0d for <spring@ietfa.amsl.com>; Mon, 16 Dec 2019 02:07:08 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 969A6120137 for <spring@ietf.org>; Mon, 16 Dec 2019 02:07:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23196; q=dns/txt; s=iport; t=1576490828; x=1577700428; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=tWnGuQAH/HzJKxVdcwpPRvKji3vwnluVyFdxfzA6yZU=; b=GWiAHWng9rrPP9Z7Lkg2oSaEMO9FZwuoJ6O1Jgqy3Un0SxU2+M8Pxfjf rZzAmnY6xb8u+GIGq+xnSFgjj44J1v3gZ4bBcZkVSvGOGJTmqZej0wlZN 9PnFqksX9xgnd6eFcobihIlSz3wBGA8Wfa2zs/gL6Y4bGWY3kCuzK998A s=;
IronPort-PHdr: 9a23:gAe0oRLbOex3befNmdmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeCtKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXE72MPfscwQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B1DADsVvdd/5xdJa1lHgELHIFzC4EcL1AFbFggBAsqhASDRgOLDIJfiVyJSYRhgS6BJANUCQEBAQwBARgBDAgCAQGDe0UCF4F7JDYHDgIDDQEBBAEBAQIBBQRthTcMhV4BAQEBAwEBEBEKEwEBLAsBCwQCAQgRAQMBAQEnAwICAh8GAQoUAwYIAgQOBQgagwGBeU0DLgEOoiQCgTiIYXWBMoJ+AQEFgTUBE0GDCA0LghcJgTaMGBqBQT+BWIJMPoIbSQEBAQEBARiBSSsJCIJSMoIsjTGDAoVViVqOWUMKgjSHKYkSgSWEQIJDdIcCkA+XG4IZj2ECBAIEBQIOAQEFgT8aDCaBWHAVGiENDIJTCUcRFI0Sg3OEWTuFP3QBAYEmjn4BAQ
X-IronPort-AV: E=Sophos;i="5.69,321,1571702400"; d="scan'208,217";a="678779983"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 16 Dec 2019 10:06:43 +0000
Received: from XCH-ALN-008.cisco.com (xch-aln-008.cisco.com [173.36.7.18]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id xBGA6g4D021949 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 16 Dec 2019 10:06:43 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-008.cisco.com (173.36.7.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 16 Dec 2019 04:06:42 -0600
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 16 Dec 2019 04:06:41 -0600
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 16 Dec 2019 05:06:41 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IBjn/ZzzE+lMfZui55WAcy9BV34YjFtlYtNPq/4j/KPRL/kgKk2ZpLiyPi07v2zd0YV8f7oFS0dqMQSBkNlSvScMD36grDfoAGKZc6BNXLD6EEYM1MEdV4Z7reAD8s+Ug9Mz7OvaAXlwyWIEUceKNTHZ7vGOls+ouRpC28i0qvRQIsmImDG+0ekI9hZgOLh+OkIp1h94BUkEVest7P3ImiQkbay8tuDHuX0jTfpP+k2QXU7hMN8f+ft89WJhHH3nf6TrZ2FsT/xWpwHtP4FJzi7a+tAJkxdImK6ZzLKR0k5ooAw2A9PO4Rjh2GyWZUgKYudFBUmqzCTv0ZbFJUCtjw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tWnGuQAH/HzJKxVdcwpPRvKji3vwnluVyFdxfzA6yZU=; b=JbEvQJnhU1iSPo6mGQpEUbzh8lKP9R1tT6BlQGRly0n7xi1kGPXE/5a8MoapLTE830RlctCdYeQhBtBXrmjIqJGXmtrLzIOAOghgVyRUT1mZdS0wKMPs1z31fjO/C+9IFa3Yp0vcGvcrXm+sUx2gEbsLBsnDEKwvzODcdRxLzp9CEQrfcImC8hWAE3gLXlMYisMvA9INz805V7t+S22956gejM+2IOCntWBb7f7cCjEiCpjNGYwxLI5fHR+UCwMYjkXD8AiKYoLTRf/8aSIy0v8/1CTifVMubA+jTDBl+sP/CLnfWRCwtMmsZ7IwkvWwimYI88lYQ/9hq1Vpk49/pA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
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=tWnGuQAH/HzJKxVdcwpPRvKji3vwnluVyFdxfzA6yZU=; b=al5qALtAQyXIjcHoqA8E1cS1ry/WcecIazoG/2Y32M3k+F5KVYbiG6J5hg6A9HGUK2T9N08+igD8PBLlYa/G5W1NO8VEA8uvXpA4S/0cA7ISLxwiyjY4MeGshenJHkb+ZpzMx2KjW23j8mdmDnCjBpMCtaxrdEC+eeFNQyKyWiA=
Received: from MWHPR11MB1600.namprd11.prod.outlook.com (10.172.53.142) by MWHPR11MB1536.namprd11.prod.outlook.com (10.172.53.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2538.16; Mon, 16 Dec 2019 10:06:40 +0000
Received: from MWHPR11MB1600.namprd11.prod.outlook.com ([fe80::884c:b80e:f787:2098]) by MWHPR11MB1600.namprd11.prod.outlook.com ([fe80::884c:b80e:f787:2098%12]) with mapi id 15.20.2538.019; Mon, 16 Dec 2019 10:06:40 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Mark Smith <markzzzsmith@gmail.com>
CC: SPRING WG <spring@ietf.org>
Thread-Topic: [spring] I-D Action: draft-ietf-spring-segment-routing-policy-06.txt
Thread-Index: AQHVs6UCoeT9WMvi1EykcMs95wQFWae78pCAgABKE/CAABgSAIAALTpA
Date: Mon, 16 Dec 2019 10:06:40 +0000
Message-ID: <MWHPR11MB16008E8034DE223FC784171EC1510@MWHPR11MB1600.namprd11.prod.outlook.com>
References: <157645488473.11514.14849824578103099190@ietfa.amsl.com> <CAO42Z2xC4_QJ4h62bC1+pdkBY4LMEkKq0zXkAxxh=RMt8GEgPw@mail.gmail.com> <MWHPR11MB1600AD626D8C052175C518ABC1510@MWHPR11MB1600.namprd11.prod.outlook.com> <CAO42Z2whbJva6OYAJ2R7iq+4t87JWF5q63LJSnVRw22TqMPfSQ@mail.gmail.com>
In-Reply-To: <CAO42Z2whbJva6OYAJ2R7iq+4t87JWF5q63LJSnVRw22TqMPfSQ@mail.gmail.com>
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=ketant@cisco.com;
x-originating-ip: [2001:420:c0e0:1004::11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c3dbcd43-697f-4b67-0f12-08d7820fa550
x-ms-traffictypediagnostic: MWHPR11MB1536:
x-microsoft-antispam-prvs: <MWHPR11MB153686712240B4F33FD0B38FC1510@MWHPR11MB1536.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 02530BD3AA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(39860400002)(136003)(376002)(396003)(199004)(189003)(13464003)(186003)(7696005)(9326002)(5660300002)(4001150100001)(6506007)(53546011)(71200400001)(316002)(55016002)(81166006)(33656002)(8676002)(8936002)(6916009)(478600001)(52536014)(21615005)(966005)(86362001)(81156014)(9686003)(76116006)(2906002)(66574012)(66946007)(66446008)(64756008)(4326008)(66476007)(66556008); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR11MB1536; H:MWHPR11MB1600.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: BCL:0;
x-microsoft-antispam-message-info: O+YhCi2lR83DZXDXaImLAvCCgAF81ADCVwQkLlqGOhSsc6Dm9Z1LLEqXKnVdpI1xpEmDNa0xgacyeueKy39kZtvt5DQh5EEJXs11Xkf2oWD/TFcz/6E0tjH8HXSPR8Ii/WgazY2d7mYoZohxBqkIgxtTbM11QyCRmJw2/WYygYvrarvoFNvlCRcFBFbeeWGgsnAq2UV0d3+6ft2cZq4X2LeibdEZgVO8re6qsmvqPgvI2bhjnwZir8DTSis/6HtGyDUZqaHaZnlZAO8AnLsp43LbCCtITAxBSCNxyHuUS6tP1Zvs3nODf0U0G5C04cweczWLPTmKqUkmCHk5fS30oosjrrvGvEHWW9DxG874Hr7S0V2Z45PoRDJUD9n3PSkzKgeA5z0lKR+pwd/wfcUv+qSxc0aWjdJSLiz4arl1kGRJZboEqEfCUrZu4/cLTrJ69TfXWsGkADcAz9+jUYAwxA8/ocnJz9uOhajCRQTiKZ/7rYgdP33IsKpAVqz1Q4JdO37OZfQWsbjjUIYdiLXzHkf0lSLAUOYB2hcRfnA81DQ=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MWHPR11MB16008E8034DE223FC784171EC1510MWHPR11MB1600namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c3dbcd43-697f-4b67-0f12-08d7820fa550
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Dec 2019 10:06:40.3933 (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: t7IuEq55p9LHdQPmVxk/GV970QWNQ2OaRHyFTTwP0gT2QC8Vr4IpLDM1IMyGVKH7eVARCSx8SXUc7COKkhjb8g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1536
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.18, xch-aln-008.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/dk7ui6UELyl1xfT0l3977p9TY4s>
Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-policy-06.txt
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: Mon, 16 Dec 2019 10:07:11 -0000

Hi Mark,

Could you share references which says it is illegal to refer to 0.0.0.0 or :: as IP addresses?

Many (if not most) implementations use these representations of IP addresses when provisioning a default static route and there is nothing wrong with doing so.

The link you shared previously that indicated an issue because someone was using these zero addresses as destination IP in the packets. That would be an incorrect analogy since there is no such proposal in this document.

Thanks,
Ketan

From: Mark Smith <markzzzsmith@gmail.com>
Sent: 16 December 2019 12:27
To: Ketan Talaulikar (ketant) <ketant@cisco.com>
Cc: SPRING WG <spring@ietf.org>; i-d-announce@ietf.org
Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-policy-06.txt


On Mon, 16 Dec 2019, 16:43 Ketan Talaulikar (ketant), <ketant@cisco.com<mailto:ketant@cisco.com>> wrote:
Hi Mark,

The draft talks about "destination of the policy" as in the tail-end node of the SR Policy. It does not talk about the destination IP address in the packet.

You can consider this as a "default policy" on similar lines as a default route.

Please see the section below which will cover one of the use-cases for steering over such SR policies to the null endpoint.
https://tools.ietf.org/html/draft-ietf-spring-segment-routing-policy-06#section-8.8.1

Hope that clarifies.


I don't think it does.

If this text is true - "The endpoint
   is specified as an IPv4 or IPv6 address" - then those are illegal IPv4 and IPv6 addresses.

If these are not being used as IPv4 or IPv6 addresses, then they cannot be referred to as IPv4 or IPv6 addresses. It is confusing and inaccurate if they are.


Thanks,
Ketan

-----Original Message-----
From: spring <spring-bounces@ietf.org<mailto:spring-bounces@ietf.org>> On Behalf Of Mark Smith
Sent: 16 December 2019 06:36
To: SPRING WG <spring@ietf.org<mailto:spring@ietf.org>>
Cc: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-policy-06.txt

"The endpoint indicates the destination of the policy.  The endpoint
   is specified as an IPv4 or IPv6 address and is expected to be unique
   in the domain.  In a specific case (refer to Section 8.8.1), the
   endpoint can be the null address (0.0.0.0 for IPv4, ::0 for IPv6)."

Per Internet Standard 3 / RFC 1122, 0.0.0.0 is an illegal IPv4 destination address.*

Per RFC 4291, ::0 is an illegal IPv6 destination address.


Regards,
Mark.


*People doing tricky things with 0.0.0.0 has cost me and a past employer 2 weeks of needless troubleshooting, delaying a product/service launch.

http://lists.ausnog.net/pipermail/ausnog/2017-July/039402.html


On Mon, 16 Dec 2019 at 11:08, <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> wrote:
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Source Packet Routing in Networking WG of the IETF.
>
>         Title           : Segment Routing Policy Architecture
>         Authors         : Clarence Filsfils
>                           Siva Sivabalan
>                           Daniel Voyer
>                           Alex Bogdanov
>                           Paul Mattes
>         Filename        : draft-ietf-spring-segment-routing-policy-06.txt
>         Pages           : 35
>         Date            : 2019-12-15
>
> Abstract:
>    Segment Routing (SR) allows a headend node to steer a packet flow
>    along any path.  Intermediate per-flow states are eliminated thanks
>    to source routing.  The headend node steers a flow into an SR Policy.
>    The header of a packet steered in an SR Policy is augmented with an
>    ordered list of segments associated with that SR Policy.  This
>    document details the concepts of SR Policy and steering into an SR
>    Policy.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-pol
> icy/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-spring-segment-routing-policy-0
> 6
> https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routin
> g-policy-06
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-po
> licy-06
>
>
> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> spring mailing list
> spring@ietf.org<mailto:spring@ietf.org>
> https://www.ietf.org/mailman/listinfo/spring

_______________________________________________
spring mailing list
spring@ietf.org<mailto:spring@ietf.org>
https://www.ietf.org/mailman/listinfo/spring