IETF Logo Mail Archive

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

"Pablo Camarillo (pcamaril)" <pcamaril@cisco.com> Tue, 07 January 2020 09:36 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 194A012008D for <spring@ietfa.amsl.com>; Tue, 7 Jan 2020 01:36:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 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.01, RCVD_IN_MSPIKE_WL=-0.01, 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=iINXSQ10; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Y0BRuivr
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 c0-gzJw8dIkW for <spring@ietfa.amsl.com>; Tue, 7 Jan 2020 01:36:55 -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 6D19C120019 for <spring@ietf.org>; Tue, 7 Jan 2020 01:36:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=40433; q=dns/txt; s=iport; t=1578389815; x=1579599415; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=cxAmXg+Dw4dl73tFnuLlm/uij5pIk/izvTr2o27Qx7E=; b=iINXSQ101Hy1Ik0KTzVbltn26OcL9RkpPkB866uWbErC2rEO40UYaJgo NEjcFORXFtlGjzeg1natUSdxADmI6zw8HYm7UheNzVeXIpKEack2DUMgV ssnNl8JAkYq9jjyH14hGGTjo0P2Qcl6gm3uE2zEchbvv7HFJcpUrxK1i7 k=;
IronPort-PHdr: 9a23:DxMZvxzO5UBW3i7XCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZudAkT+JeTrawQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CSAABQUBRe/5hdJa1mHAEBAQEBBwEBEQEEBAEBgWkGAQELAYEkL1AFbA5KIAQLKgqDf4NGA4sDgjolmA2BLhSBEANUCQEBAQwBAS0CAQGEQAIXgVIkNQgOAgMNAQEEAQEBAgEFBG2FNwyFXgEBAQEDEhEdAQE3AQ8CAQgOAwMBAQEhAQYDAgICMBQJCAIEDgUigwABgXlNAy4BoVwCgTiIYXWBMoJ+AQEFgkqCNxiCDAmBNgGMGBqBQT+BEScMFIIeLj6CZASBLgESATYJFoJaMoIsjT6DA4VXiWWPJgqCNpYcG4JHh32QG4RBpHMCBAIEBQIOAQEFgVMBN2dxcBVlAYJBUBgNjRIMF4NQilN0AYEnixKBIgGBDwEB
X-IronPort-AV: E=Sophos;i="5.69,405,1571702400"; d="scan'208,217";a="690645280"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Jan 2020 09:36:54 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 0079as3C032556 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 7 Jan 2020 09:36:54 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 7 Jan 2020 03:36:53 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 7 Jan 2020 03:36:53 -0600
Received: from NAM12-BN8-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; Tue, 7 Jan 2020 04:36:53 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=APT9w0tIaOCPFQGrgt+YTynKi09Zxd/0+KQRYvzSk92Yl2MqWb8MHGaKkAMRCyZ0B/mOf3fKCtedmAtd7RyRBQagKxVACowRrpgecZB62ydcZ2zUlKKJduwnZTIXxnT4YzksWYIPZ3dpYBw+xef7+9y+zi8h5QxOJ+9R49Xm9NRpMXnjyK89gbXmo7uf+LTwGLqDKXqBs4ImBI61OewNi0Z50e3AaUa+k/7bW/ZW0fDCVYbaHeWwbNQoHY9Ov4WV3j+azS0tv2vxgxB/LhVNJX33r66eINJRGNuxF3QOEuM8dZ1x5/NlKVpXlejFPpmiyV1IeGqAjPaC1yOVDVgFmA==
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=cxAmXg+Dw4dl73tFnuLlm/uij5pIk/izvTr2o27Qx7E=; b=jdmUqTx6URppBN7l1x5XUDTR9A+xpHfkcDBIT7mc8nUx3WNKlmjsEWnHd8Ke43GnC5IrswWzwLXLVjGs0GpYvbxSt1W1jtUrn0+zl0Mawvts+GHyF9qdmEodr8ohEIeWOIndzBukgIoTItjOBQ+VMcD0EWyP+7JGJ19nvpq/U8gS9hs5pfog7V5aJypJ3g1QQukAQELASsdkll7H4XvMIIiDU7ifhu2/JOC5qCsCm5bX9t34+Tf0CjeNPRxmehystDCU5yLIL9DHtZlIdxgcgfZIFJycgQAh+p9j1z1BYQhU9ApvcLQtF9b1X31bBX/RK2zoUYEn5xH5ooVjDAbiJw==
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=cxAmXg+Dw4dl73tFnuLlm/uij5pIk/izvTr2o27Qx7E=; b=Y0BRuivr2KHcKQGEdWQdTXIsgWtdEdsqwRR2vkjBmhq1+dpwbkcjhzjbmGXHn3dihiAhJRioPIIRmIgBnC0i1NAD3gkKJcewvkaI9/wEpNtmkvoV5fh5hypA63Z2MjdJRVKvbdssIpdtc/Qow8LSgclsJ8a97zOkIcUU6teSwTg=
Received: from MWHPR11MB1374.namprd11.prod.outlook.com (10.169.234.8) by MWHPR11MB1312.namprd11.prod.outlook.com (10.169.237.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2602.12; Tue, 7 Jan 2020 09:36:51 +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.2602.016; Tue, 7 Jan 2020 09:36:51 +0000
From: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
To: Ron Bonica <rbonica@juniper.net>
CC: SPRING WG <spring@ietf.org>
Thread-Topic: [spring] SRv6 Network Programming - ICMP Source Address Selection
Thread-Index: AQHVt1sjI5E9vezZDUu0pc5hCyLTq6fFADeQgBI8Q4A=
Date: Tue, 07 Jan 2020 09:17:33 +0000
Message-ID: <44F0ED35-5684-4594-BB29-BDCC193284A4@cisco.com>
References: <B91AA98B-F605-4C6B-AFAF-C9FDEA703460@cisco.com> <BN7PR05MB5699B27F84C5E8051028D97AAE2C0@BN7PR05MB5699.namprd05.prod.outlook.com>
In-Reply-To: <BN7PR05MB5699B27F84C5E8051028D97AAE2C0@BN7PR05MB5699.namprd05.prod.outlook.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.45]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 35983b17-4166-4233-4086-08d793552024
x-ms-traffictypediagnostic: MWHPR11MB1312:
x-microsoft-antispam-prvs: <MWHPR11MB131280569BD4AF07834F32A1C93F0@MWHPR11MB1312.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 027578BB13
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(396003)(136003)(346002)(376002)(366004)(199004)(189003)(316002)(8936002)(86362001)(5660300002)(36756003)(6916009)(76116006)(91956017)(2906002)(66476007)(66946007)(186003)(478600001)(53546011)(6666004)(8676002)(6506007)(66556008)(64756008)(66446008)(81166006)(81156014)(26005)(6512007)(33656002)(4326008)(6486002)(71200400001)(2616005); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR11MB1312; H:MWHPR11MB1374.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: wFsETnZAY1FYfVF4kKugX2kW5m+o29CYo4dXyGhgk+2Wx5/t9jLzpeb83PIcn1PU62/6sUMuwiijryNVoBSufpleQvcKr0+vYY7ojL7ET9MazZm1iXLPuqqOs3Nw4mx2sr+CcgAS+GXqZcOLnn99P3cnqXyw8Zm1eShvrX0IuuL3NgmQCp4G5TpavfRpR+siwWdGUyZ3kDqH7xggGe0zhSzn2Jas5Ecs09O1pN0qOWZ7t8lWWdgUiHkU0heFQ9MCPbgssZjP+1UXL3d+KliFoCYUb9kdmuPH/I1eY6nUy3cCYkRlRyX7uJDPqt9fDG96ZmrhM1942528rzDjf3cUrubhjG8Hvce4EkXGHJTqgkcNQSrA+YvIxVwni8rZKHJVJH5Ug2q8rUQHWhIWChGMR9+Yk6x8FSLzBnSYTiOClrxcOZyhjzCDBJshKdNn/VVN
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_44F0ED3556844594BB29BDCC193284A4ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 35983b17-4166-4233-4086-08d793552024
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jan 2020 09:36:51.6074 (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: Sro5nXu/YtNZX+Jl9t8lrjMHeVgQj+qmZOwXcIXqVbxb0yLWHCBO3SEIuYtA15rdufdHhMujfvLgO58D2866sA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1312
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/m3ED_UPVaqMKEkg8xoS-ZEB-5dI>
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: Tue, 07 Jan 2020 09:36:58 -0000

Ron,

It’s good to see agreement on the fact that SRH follows RFC4443 Section 2.2 with respect to how the ICMP Source Address is selected.

Can you please point me to the text in draft-ietf-spring-srv6-network-programming that changes the behavior below from RFC4443 Section 2.2? I believe there is no such text.

Thanks,
Pablo.

From: Ron Bonica <rbonica@juniper.net>
Date: Saturday, 21 December 2019 at 20:59
To: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
Cc: "spring@ietf.org" <spring@ietf.org>
Subject: RE: [spring] SRv6 Network Programming - ICMP Source Address Selection

Pablo,

Section 2.2 of RFC 4443 offers the following options:

“   (a) If the message is a response to a message sent to one of the
       node's unicast addresses, the Source Address of the reply MUST be
       that same address.

   (b) If the message is a response to a message sent to any other
       address, such as

       - a multicast group address,
       - an anycast address implemented by the node, or
       - a unicast address that does not belong to the node

      the Source Address of the ICMPv6 packet MUST be a unicast address
      belonging to the node. “

So, the question boils down to whether you consider a SID to be one of the node’s unicast addresses. If so, the answer is a). If not, the answer is b).

So, which is it?

                                                    Happy Holidays,
                                                         Ron





Juniper Business Use Only
From: Pablo Camarillo (pcamaril) <pcamaril@cisco.com>
Sent: Friday, December 20, 2019 12:30 PM
To: Ron Bonica <rbonica@juniper.net>
Cc: spring@ietf.org
Subject: Re: [spring] SRv6 Network Programming - ICMP Source Address Selection

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<mailto:spring-bounces@ietf.org>> on behalf of Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org<mailto:rbonica=40juniper.net@dmarc.ietf.org>>
Date: Thursday, 19 December 2019 at 14:59
To: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>, "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto: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<mailto:pcamaril@cisco.com>>
Sent: Thursday, December 19, 2019 6:47 AM
To: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>; spring@ietf.org<mailto: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