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

"Pablo Camarillo (pcamaril)" <pcamaril@cisco.com> Tue, 14 January 2020 18:02 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 1A12F1200D7 for <spring@ietfa.amsl.com>; Tue, 14 Jan 2020 10:02:05 -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=fBW9kp78; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=LpNKO90I
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 a0vnBC4kRj5O for <spring@ietfa.amsl.com>; Tue, 14 Jan 2020 10:01:58 -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 7F95312098C for <spring@ietf.org>; Tue, 14 Jan 2020 10:01:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=82869; q=dns/txt; s=iport; t=1579024918; x=1580234518; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=h0McWj4OZ802jWcXog4R9gcfWW0bnWaFYYCuDNELzB0=; b=fBW9kp78kUUtuYXHoX/wv0grXS2lVwPjAePSM2Wd9sg2DnSwtWaRsC5V m1bNJ0BaTKN6ORoykxOTrW11VU/L8yODZDoEPKqR4VgKREDKkysrfVoby OvtwpZ+99FeBYR6WlxZ80BXcfJa6yfuFxT8bf+gW+JoAUdGrGFeTnXXYQ o=;
IronPort-PHdr: =?us-ascii?q?9a23=3AQkbQihF5JyIP6qW0bIv6/Z1GYnJ96bzpIg4Y7I?= =?us-ascii?q?YmgLtSc6Oluo7vJ1Hb+e4z1Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNV?= =?us-ascii?q?cejNkO2QkpAcqLE0r+eebhZikzBsVGfFRk5Hq8d0NSHZW2ag=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BEAAA3AR5e/5RdJa1mGwEBAQEBAQE?= =?us-ascii?q?FAQEBEQEBAwMBAQGBaQQBAQELAYEkL1AFbA5KIAQLKgqEA4NGA4sEgjolmA6?= =?us-ascii?q?BLhSBEANUCQEBAQwBAS0CAQGEQAIXgWckNgcOAgMNAQEEAQEBAgEFBG2FNwE?= =?us-ascii?q?LhV4BAQEBAxIICR0BATcBDwIBCBEDAQEBIQEGAwICAjAUCQgCBA4FIoMEAYF?= =?us-ascii?q?9TQMuAaE9AoE4iGF1gTKCfgEBBYJEgmMYggwJgTYBjBcagUE/gREnDBSCHi4?= =?us-ascii?q?+gmQEgS4BEgE2CRaCWjKCLI1HgweFV4lvjy4KgjiWLRuCR4gCjEiDXIRCihU?= =?us-ascii?q?EmncCBAIEBQIOAQEFgVkJKWdxcBVlAYJBUBgNiAEMF4NQilN0AYEniUuBIgG?= =?us-ascii?q?BDwEB?=
X-IronPort-AV: E=Sophos;i="5.70,319,1574121600"; d="scan'208,217";a="416840343"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 14 Jan 2020 18:01:57 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id 00EI1vtg006220 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 14 Jan 2020 18:01:57 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 14 Jan 2020 12:01:56 -0600
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 14 Jan 2020 12:01:56 -0600
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 14 Jan 2020 12:01:56 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=T5xFmxEnlBHJTqYtUJlZ3DdW3rpOeVtYz32nJckGSnTppErhPH16hkx1UcNrq97749zFHvG3SA/YGLFelb8590IR3uN+xzNb4+sY3asDHC5lkkPaNRJ2+rta+JthgNOkSx2KVWK8PrhGFJbkDsFIFO/GxLCY/lWhEfpJQuo87IlaUdJ1nzRWGv73DxBGXF6E/jVjN2xJ1fOhzpsKKzfSTu9W6IY4b2Qa99YIgHkaBQBHBxoTgJKoObgnz6ewp63ps1xQoKtt21fBi2MKYyQLJOSwhuF6BqkVVxowtSdG78S4eG5FrmL0fvLTqH86WHrAD4t0996s34RkFhXsOo3arA==
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=h0McWj4OZ802jWcXog4R9gcfWW0bnWaFYYCuDNELzB0=; b=MjZwSV4Yw/Q9tWW/j1+jzeM3b9ZTRj+HXSOwCkGnfpGXEoibD5T3NmG40REepWy0SLJerFFm5zuio9pIUBM8B9ER6hbZ4lh2dfSeYNs73awEKt3O3+QEz14lWwe7/nQTf22i5I4fIW5bCtMeUR9cA4fjKyhWAxBXBh3akvWYIn2AX5Mio5pk+EmchvZUsz2k4V3K0n5sMf6rs7p4JXRbtHF9HlI20L6zJhDwLm4q8BGlmFHFQ5bGdRSUhEs+ymttODn3XZyW9EWp+YwzNP1FIbBaxGnKHNJHECXDpMXz2UR1MTgRRAHCXsx1KzyeVtDs3dVEzwl0xuPFeiMprU4ihg==
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=h0McWj4OZ802jWcXog4R9gcfWW0bnWaFYYCuDNELzB0=; b=LpNKO90IWM1npeVFZu1FNbyeHzefBYhT7Z94snVAT02Nj6f5pogEFXXrOt10MT5Y+L4LgBSE0jkUZBQzFqQI5OAtZs/TRQiYPbbkqjn9hH2tru1PhagKkDb94T5R+mnOrv78XDJRxuo/amZTGthAICu+pBFgcgNV9bo9u5/Ajpw=
Received: from MWHPR11MB1374.namprd11.prod.outlook.com (10.169.234.8) by MWHPR11MB1742.namprd11.prod.outlook.com (10.175.55.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2623.8; Tue, 14 Jan 2020 18:01:53 +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.2623.017; Tue, 14 Jan 2020 18:01:53 +0000
From: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>
To: "rbonica@juniper.net" <rbonica@juniper.net>
CC: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] SRv6 Network Programming - ICMP Source Address Selection
Thread-Index: AQHVt1sjI5E9vezZDUu0pc5hCyLTq6fFADeQgBI8Q4CACFa2YIAEu/GAgAASX9CABK7rAIAAEWrAgAGEk4A=
Date: Tue, 14 Jan 2020 17:43:51 +0000
Message-ID: <94AA5F04-2458-42B0-AA7E-7039EA795C1C@cisco.com>
References: <B91AA98B-F605-4C6B-AFAF-C9FDEA703460@cisco.com> <BN7PR05MB5699B27F84C5E8051028D97AAE2C0@BN7PR05MB5699.namprd05.prod.outlook.com> <44F0ED35-5684-4594-BB29-BDCC193284A4@cisco.com> <BN7PR05MB39386FA6A2666370FF07FAA7AE3F0@BN7PR05MB3938.namprd05.prod.outlook.com> <CEB721B4-DA87-4838-BA6D-499D38A33936@cisco.com> <BN7PR05MB3938FEE1C2F83C919D4CFA2AAE380@BN7PR05MB3938.namprd05.prod.outlook.com> <DF0DC4A0-37D7-4943-BFC2-D152BB9E8D38@cisco.com> <BN7PR05MB39381FB65ED5B034D21267F0AE350@BN7PR05MB3938.namprd05.prod.outlook.com>
In-Reply-To: <BN7PR05MB39381FB65ED5B034D21267F0AE350@BN7PR05MB3938.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.43]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5d391c52-046c-474c-187a-08d7991bd605
x-ms-traffictypediagnostic: MWHPR11MB1742:
x-microsoft-antispam-prvs: <MWHPR11MB174242C8D5EC5CCD5E5D8F56C9340@MWHPR11MB1742.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 028256169F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(39860400002)(136003)(346002)(396003)(366004)(189003)(199004)(36756003)(4326008)(6916009)(2616005)(316002)(71200400001)(81156014)(5660300002)(86362001)(8936002)(81166006)(8676002)(26005)(6486002)(2906002)(186003)(6506007)(53546011)(6512007)(478600001)(66446008)(64756008)(66556008)(33656002)(91956017)(66476007)(76116006)(66946007)(579004); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR11MB1742; 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: jnWA7iHmIJv8c34HXDTv1jrCW4RDYdFZeuFezKqL01N8hvKg0mnH8GN1ccRXENJD4rHplpWg8ywZMpfwOO4qxpHh2ylIKsk1z4+3d2yJkSBmDsIlpZTcKmLBapdhY+VBXVPNbEYwxccWy1Uusibc81stHcHGS8zZD0rN9rrOi2FhdypafiE0Ii2Fq2DD5E9nwRzeXT6thW1r4s2nlz18RN9mjScwl+zkULkGOq3UEE0UveuoqZKlYe1s3dgsB3Wt5ZONX7URhrQFbRLkXLwCMoPtYShxaFm/2d12cnCSjc/6J9xCju6yKC51tEsye1/cTktuQQhHKNsO59ktVzg1VVtwNGrvcEajAKeaVkRVV22XTSJlna7H4iQuG8m8C2fAvV0Ycu0kMNr3V6MgZTNCWp7nzwv7Zu2FmumAxJPhT3eTfexC+JWgljEkMwIYaGbj
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_94AA5F04245842B0AA7E7039EA795C1Cciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5d391c52-046c-474c-187a-08d7991bd605
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jan 2020 18:01:52.9019 (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: yc5CdNZPgayJVimCuzML2Cvmwl7tyQCLfJ4U1J1bna1M88kJw+9Y/rKefdAwvdNrHhayxS+Plh2jleC5FFXEEQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1742
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.18, xch-rcd-008.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/XmD9p2ylPmLTO2jbNpnlwdPkbqs>
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, 14 Jan 2020 18:02:05 -0000

Ron,

As a matter of fact we cannot “unequivocally state that a SID is a unicast address” always. Simple reason: RFC8402 - “3.3.  IGP-Anycast Segment (Anycast-SID)”.

Cheers,
Pablo.

From: Ron Bonica <rbonica@juniper.net>
Date: Monday, 13 January 2020 at 20:41
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,

The problem isn’t a statement in the network programming draft. It is an omission in the network programming draft.

If the network programming draft unequivocally stated that a SID is a unicast address of the instantiating node, the following text from RFC 4443 would apply:


“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.”


If the network programming draft unequivocally stated that a SID is a not unicast address of the instantiating node, the following text from RFC 4443 would apply:


If the message is a response to a message sent to any other address, the Source Address of the ICMPv6 packet MUST be a unicast address belonging to the node.

                                                                                                            Ron



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

Ron,

You cannot pre-select or enforce one of the two options you refer to below.

The ICMP behaviors/considerations for SRv6 NET-PGM are the same as in the SRH.
It boils down to: when you generate an ICMP Parameter Problem Message you follow the logic described in RFC4443 section 2.2 to choose the source address of the packet.
RFC4443 offers two options A and B.
In your implementation you need to develop both options and depending on the type of address you will choose either A or B. It is not possible to create an implementation shortcut and pre-select/enforce only one of them.

Can you please point me to the text in draft-ietf-spring-srv6-network-programming that suggests that the ICMP considerations are changed with respect to the SRH? I believe there is none.

Thank you,
Pablo.

From: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>
Date: Friday, 10 January 2020 at 20:09
To: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>
Cc: "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,

So, in Section 4.1, Line S03, an SRv6 node sends an ICMP Parameter Problem Message. What is the source address in that message?

Is it the destination address of the offending packet (i.e., A SID)? Or is in the address of an interface on the SRv6 node?

                                                                                         Ron




Juniper Business Use Only
From: Pablo Camarillo (pcamaril) <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>
Sent: Friday, January 10, 2020 11:54 AM
To: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>
Cc: spring@ietf.org<mailto:spring@ietf.org>
Subject: Re: [spring] SRv6 Network Programming - ICMP Source Address Selection

Ron,

There is no behavior in draft-ietf-spring-srv6-network-programming that proposes to encode a SID in the source address of the IPv6 header.

If in the future someone would propose to do such thing in another I-D; it is up to those authors to justify why they would want to do this, and how to ensure that the processing does not break any other protocol. But as said, this is not in the scope of draft-ietf-spring-srv6-network-programming.

Regarding the ICMP messages:
SRH follows RFC4443 Section 2.2 with respect to how to select the ICMP Source Address.
SRv6 Network Programming does not change this (it simply follows the SRv6 rules defined by the SRH).

In your email you refer to a possibility of future protocols breaking this. I don’t think that we can guess what future protocols will do, and it is up to those future protocols to ensure compatibility with the existing standards.

Thanks,
Pablo.

From: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>
Date: Tuesday, 7 January 2020 at 19:07
To: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>
Cc: SPRING WG <spring@ietf.org<mailto:spring@ietf.org>>
Subject: RE: [spring] SRv6 Network Programming - ICMP Source Address Selection

Pablo,

Let me try to ask the question another way:


1)      Is it generally acceptable for a SID to appear in the source address field of an IPv6 header?

2)      Can an exception be made for ICMP messages?

I think that the answer to the first question is “no”, because doing so would break ICMP. Think about what would happen if:


-          Node S sends a packet to Node D with a SID S as its source address.

-          Node Q is an intermediate node on the path from Node S to Node D. For some reason, Node Q cannot forward the packet.

-          Node Q sends an ICMP message to Node S. The ICMP destination address is SID S.

-          The ICMP message arrives at Node A

-          Node A discards the ICMP message, because the payload is ICMP

It might be OK to make an exception for ICMP messages. This is because RFC 4443 forbids sending an ICMP message in response to another ICMP message. However, I am not entirely sure that this is a good idea. One day in the future, some protocol other than ICMP may try send a response to the source address of the ICMP message.

                                                                                     Ron




Juniper Business Use Only
From: Pablo Camarillo (pcamaril) <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>
Sent: Tuesday, January 7, 2020 4:18 AM
To: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>
Cc: SPRING WG <spring@ietf.org<mailto:spring@ietf.org>>
Subject: Re: [spring] SRv6 Network Programming - ICMP Source Address Selection

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<mailto:rbonica@juniper.net>>
Date: Saturday, 21 December 2019 at 20:59
To: "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com<mailto:pcamaril@cisco.com>>
Cc: "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,

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<mailto:pcamaril@cisco.com>>
Sent: Friday, December 20, 2019 12:30 PM
To: Ron Bonica <rbonica@juniper.net<mailto:rbonica@juniper.net>>
Cc: spring@ietf.org<mailto: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

Please excuse any typos, sent from my 'smart'phone.

Please excuse any typos, sent from my 'smart'phone.

Please excuse any typos, sent from my 'smart'phone.