IETF Logo Mail Archive

Re: [spring] SRv6 Network Programming - ICMP Source Address Selection

"Pablo Camarillo (pcamaril)" <pcamaril@cisco.com> Fri, 20 December 2019 17:30 UTC

Return-Path: <pcamaril@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 40CA6120856 for <spring@ietfa.amsl.com>; Fri, 20 Dec 2019 09:30:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, 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=Yv93C1xK; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=N0ice8zp
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 tNfwZxC2EWLz for <spring@ietfa.amsl.com>; Fri, 20 Dec 2019 09:30:19 -0800 (PST)
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 6D0E912084D for <spring@ietf.org>; Fri, 20 Dec 2019 09:30:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26107; q=dns/txt; s=iport; t=1576863019; x=1578072619; h=from:to:cc:subject:date:message-id:mime-version; bh=6P9QkDV5S6izvxxOHsxJgDH4Isy+3nrnCaUFX+EHXZA=; b=Yv93C1xKKH2zVBCGHAHKkK9/V8zXcoyre/KiTGRZmioUCrtdPQk9O+EH 410f+tBf5QhyyBERnMatLf9Pl1m/OoEjrhEXbH0cdKF/Uz1wzCITbpT09 yvFApHx/eSRk9RG2ACm2hFLEFPxTzJQzBa2jEe6XTmzFMyVkCgFY+3zjP 0=;
IronPort-PHdr: 9a23:27Q5kxNrb2uZ3o/DpHwl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu6w/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBjjJ/fvZjY7GOxJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AFAwC3A/1d/5hdJa1lHQEBAQkBEQUFAYFrBQELAYEdL1AFbA5KIAQLKgqDfYNGA4pzgl+YCIFCgRADVAkBAQEMAQEtAgEBhEACF4IFJDcGDgIDDQEBBAEBAQIBBQRthTcMhV4BAQEBAxIRHQEBNwERAQgOAwMBAQEhBwMCBDAUCQoEDgUigwABgXlNAy4BoQoCgTiIYXWBMoJ+AQEFgkqCTRiCDAmBNgGMGBqBQT+BOCCCHi4+gmQEgS4BEgE/FoJaMoIsjTWDA4VXiWGPIQqCNJYYG5pVhEGkZAIEAgQFAg4BAQWBaCNncXAVZQGCQVAYDY0SDBeDUIpTdAGBJ5AIgSIBgQ8BAQ
X-IronPort-AV: E=Sophos;i="5.69,336,1571702400"; d="scan'208,217";a="397258671"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 20 Dec 2019 17:30:18 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id xBKHUIH3003126 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 20 Dec 2019 17:30:18 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 20 Dec 2019 11:30:17 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 20 Dec 2019 12:30:16 -0500
Received: from NAM10-MW2-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; Fri, 20 Dec 2019 12:30:16 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=S+UiZoVKHYciNhjiJPrkOJaB0aFt07EdQ6ByruGvTdHXSIPKj5FmFVSl+thMOowddcRSz95dkhazskIF3TfQokaoWp66H9Uoh0uN6yaiMl6Ns6TWGrep2cDLBaVyHoD6CqPiw35UMxnAwQQD3HxwAxFNZzMMALUXOmE84uZ7J4RuRzeWvOfBvkdWeTef3uwOixVNpOjQMkKfoAc28bKq8vys+ArRGfGXDKKzqplIrgxRdifp6yd/htVMMwSb8ZOmOacV8326hHPqLlE1OuAd+qQSv5EhbAi+MCNc49fsfA2PrnmHcNuT5srLCUnF44S6zCzsyx67Obosle/Gt2RIew==
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=6P9QkDV5S6izvxxOHsxJgDH4Isy+3nrnCaUFX+EHXZA=; b=m4m3C1CEui80zK0WJxvx/mERWu8Hcc+9ORyXeMIjN/o/2IORz5SKmLnkSZNZDn1cALHwMtm1VHoc5gjq0IK12O6BCtM3M6FHBeWbrKuqTnJutxzMI+ysmp+q58PAAgojrdGGJpMmB93Nc76ecmphuepeECUydpXcsJ7KyYj5zRAIpA9Mm0ehHKbT1Nks1HXV1s8VtYScZaqVS23oZBkx1F0IAzKLwX5x8T15+6OAR/xRWmtU+vMcrr35u9HqJDBLNTWCbwXrVUkg+m+d2TmIdXCxSWkwOimHkCDTfOBR8vzwrYcYhYx6Ewji15MkLJWwQg1mnPeS7u+ImIcf2WeOaA==
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=6P9QkDV5S6izvxxOHsxJgDH4Isy+3nrnCaUFX+EHXZA=; b=N0ice8zpGRufKKzG2hE+DZnRjGXnNWQvRUJoRTtTV6dz/55fGbWswqEmyDxTsdfhikMUqKCUFgaNfuzel1poEBf1uxgVBHIELknCXgiIi/LgBAuHM6Fruh4ycF6+Svtv5A36ncKLRapj/ezsd5BEg9fj6/4GFxAlzwEi8u1SH+k=
Received: from MWHPR11MB1374.namprd11.prod.outlook.com (10.169.234.8) by MWHPR11MB1567.namprd11.prod.outlook.com (10.172.54.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.15; Fri, 20 Dec 2019 17:30:15 +0000
Received: from MWHPR11MB1374.namprd11.prod.outlook.com ([fe80::b04b:c9bb:2378:7a8d]) by MWHPR11MB1374.namprd11.prod.outlook.com ([fe80::b04b:c9bb:2378:7a8d%11]) with mapi id 15.20.2559.016; Fri, 20 Dec 2019 17:30:15 +0000
From: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
To: Ron Bonica <rbonica@juniper.net>
CC: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] SRv6 Network Programming - ICMP Source Address Selection
Thread-Index: AQHVt1sjI5E9vezZDUu0pc5hCyLTqw==
Date: Fri, 20 Dec 2019 17:30:15 +0000
Message-ID: <B91AA98B-F605-4C6B-AFAF-C9FDEA703460@cisco.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.20.0.191208
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pcamaril@cisco.com;
x-originating-ip: [173.38.220.35]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fa6b2589-d78a-4d1d-2ecf-08d785724687
x-ms-traffictypediagnostic: MWHPR11MB1567:
x-microsoft-antispam-prvs: <MWHPR11MB1567C7B01BA1943D4725635CC92D0@MWHPR11MB1567.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 025796F161
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(376002)(136003)(346002)(366004)(39860400002)(189003)(199004)(71200400001)(4326008)(86362001)(2906002)(316002)(6916009)(478600001)(6486002)(81156014)(81166006)(6506007)(53546011)(186003)(36756003)(8936002)(26005)(33656002)(8676002)(6512007)(5660300002)(2616005)(66556008)(66476007)(64756008)(66446008)(66946007)(91956017)(76116006); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR11MB1567; H:MWHPR11MB1374.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: BCL:0;
x-microsoft-antispam-message-info: /wnTmeZ1GLT8/YlhomhFWsVnC2n/innm1eD/C8keC9jiv5ckRkRumb1Pi0dy3UgTgUsZMwN+bWEc/VOtedUQ8wGLM1bzIDljSqQzWpIfWMtADBE9j/QcHEJnY03Hjo86jeZkQFBWqgGkT79SMxITfEoSwBHWvOPUunyTjPqRQ3lImFYpOh51ty0zHa8Fz1/4oQCRtlKUBm3Mo4LDMvRqD+t7p28A1da7Hr7265Zp3WFR2mmzf3AMduC16yKzXmqX3TWg2xgyN0uthB2nqr/kQfTgl0Sd5Nq0VA/mY6IkFGDX3gQwg6EccRnZvfUenz6vQHCVxLgYTxjcHdv4Uo1iq9FD+ja79jQsUkdGefX/cRHwPbrksifZ8WSgtMiBlobVrKL7S0u4P7jq7pH4I+9hYMxbiz+NQyYlE85lpzOCXpniszWsndcQwspSQvix1Ev3
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_B91AA98BF6054C6BAFAFC9FDEA703460ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: fa6b2589-d78a-4d1d-2ecf-08d785724687
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Dec 2019 17:30:15.1895 (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: t702GufWdw0qDjeio3mYOaJMfiVKIWkNOrDkt0JT23czHS4M0/z0Detl+DaZC/eG4Hc0qtyhVPvB8SLI+2kbEg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1567
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/nyYCBkqvol5WYj0rcKsg3gS-LXA>
Subject: Re: [spring] SRv6 Network Programming - ICMP Source Address Selection
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: Fri, 20 Dec 2019 17:30:21 -0000

Ron,

I guess that draft-ietf-6man-segment-routing-header does not contain any explicit text about it because it is not needed.
Instead draft-ietf-6man-segment-routing-header contains a reference to RFC4443 that details in section 2.2 how to select it.

There is no text in draft-ietf-spring-srv6-network-programming that changes such behavior.

Happy Holidays,
Pablo.

From: spring <spring-bounces@ietf.org> on behalf of Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
Date: Thursday, 19 December 2019 at 14:59
To: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>, "spring@ietf.org" <spring@ietf.org>
Subject: Re: [spring] SRv6 Network Programming - ICMP Source Address Selection

Pablo,

Can you provide a specific reference into draft-ietf-6man-segment-routing-header? I can’t find the answer to my question in there.

                                                                                         Ron





Juniper Business Use Only
From: Pablo Camarillo (pcamaril) <pcamaril@cisco.com>
Sent: Thursday, December 19, 2019 6:47 AM
To: Ron Bonica <rbonica@juniper.net>; spring@ietf.org
Subject: Re: SRv6 Network Programming - ICMP Source Address Selection

Ron,

This is exactly the same as in the SRH.
There is no text in draft-ietf-spring-srv6-network-programming that changes this.

Cheers,
Pablo.

From: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>
Date: Monday, 9 December 2019 at 23:48
To: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>, SPRING WG <spring@ietf.org<mailto:spring@ietf.org>>, 6man <6man@ietf.org<mailto:6man@ietf.org>>
Subject: RE: SRv6 Network Programming - ICMP Source Address Selection

Pablo,

Section 2.2 of RFC 4443 offers two options. If you think that a SID is a unicast address, the first option is applicable. If you think that a SID is not a unicast address, the second option is applicable.

Which did you choose?

                                                                         Ron



Juniper Business Use Only
From: Pablo Camarillo (pcamaril) <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>
Sent: Monday, December 9, 2019 10:18 AM
To: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>; SPRING WG <spring@ietf.org<mailto:spring@ietf.org>>; 6man <6man@ietf.org<mailto:6man@ietf.org>>
Subject: Re: SRv6 Network Programming - ICMP Source Address Selection

Ron,

As you pointed out in your email, RFC4443 Section 2.2 is very clear about how to select the source address.
draft-ietf-spring-srv6-network-programming does not change this.

Thanks,
Pablo.

From: ipv6 <ipv6-bounces@ietf.org<mailto:ipv6-bounces@ietf.org>> on behalf of Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org<mailto:rbonica=40juniper.net@dmarc.ietf.org>>
Date: Friday, 6 December 2019 at 17:40
To: SPRING WG <spring@ietf.org<mailto:spring@ietf.org>>, 6man <6man@ietf.org<mailto:6man@ietf.org>>
Subject: SRv6 Network Programming - ICMP Source Address Selection

Authors,

When an SRv6 node sends an ICMP message, how does it select the ICMP message’s source address?

Section 2.2 of RFC 4443 offers two options. If you think that a SID is a unicast address, the first option is applicable. If you think that a SID is not a unicast address, the second option is applicable.

                                                                     Ron


Juniper Business Use Only

v2.23.0 | Report a Bug | By Email