Re: [Softwires] [Idr] [bess] Regarding the Next Hop Network Address coding for IPv4 VPN over IPv6 Core in RFC5549

"Vigoureux, Martin (Nokia - FR/Paris-Saclay)" <martin.vigoureux@nokia.com> Thu, 27 June 2019 10:36 UTC

Return-Path: <martin.vigoureux@nokia.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD6F0120219; Thu, 27 Jun 2019 03:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 WDSuxQ_IdCp3; Thu, 27 Jun 2019 03:36:50 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50138.outbound.protection.outlook.com [40.107.5.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E704312060D; Thu, 27 Jun 2019 03:36:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ZsMQuvT2aY6CR1TEOUExOB5PL7F1O+Nzk2AwP1DvbHo=; b=o15VIU+6CRhe5/87/zKd2abpZqwamCOKQ4m4ILWr4t95mv+fS42KZR37JOKcf0onH7y9vjvdreHJ84Aq08E1WE9KvfzCBKdFhg4w/n5XFQ8VkWGw61dWeh05zmt4/wjmX8yDRUe4XLS6ugOhtLy3/tukTXHXuWQxUsSgMqiEgvQ=
Received: from DB7PR07MB5483.eurprd07.prod.outlook.com (20.178.84.145) by DB7PR07MB5307.eurprd07.prod.outlook.com (20.178.44.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2032.12; Thu, 27 Jun 2019 10:36:46 +0000
Received: from DB7PR07MB5483.eurprd07.prod.outlook.com ([fe80::a86f:c763:bc8a:9943]) by DB7PR07MB5483.eurprd07.prod.outlook.com ([fe80::a86f:c763:bc8a:9943%6]) with mapi id 15.20.2008.018; Thu, 27 Jun 2019 10:36:46 +0000
From: "Vigoureux, Martin (Nokia - FR/Paris-Saclay)" <martin.vigoureux@nokia.com>
To: Xiejingrong <xiejingrong@huawei.com>, Alexander Okonnikov <alexander.okonnikov@gmail.com>, Robert Raszuk <robert@raszuk.net>, "bess@ietf.org" <bess@ietf.org>
CC: "softwires@ietf.org" <softwires@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] [bess] [Softwires] Regarding the Next Hop Network Address coding for IPv4 VPN over IPv6 Core in RFC5549
Thread-Index: AQHVLNQ3mv8wvOBs4U+t9QxIO2nPpg==
Date: Thu, 27 Jun 2019 10:36:45 +0000
Message-ID: <9670cbbf-9b35-7ac4-b809-529ab59f18a9@nokia.com>
References: <19AB2A007F56DB4E8257F949A2FB9858E5BDBB89@NKGEML515-MBS.china.huawei.com> <9DB8FCD5-DD04-4EB1-AEA5-A33B5B6F1BC4@gmx.com> <19AB2A007F56DB4E8257F949A2FB9858E5BE201C@NKGEML515-MBS.china.huawei.com> <B577834D-4010-42DF-AF28-690A1BD2A5AC@telekom.de> <16253F7987E4F346823E305D08F9115AAB8D61CE@nkgeml514-mbx.china.huawei.com> <CAOj+MMGdoi1ROTmbuFu8eXWix6JfYwO1TCPUakyOEdTU01-1zA@mail.gmail.com> <B17A6910EEDD1F45980687268941550F4D87EC92@MISOUT7MSGUSRCD.ITServices.sbc.com> <8E1E4882-7850-4BF4-82EC-82BDFE9BF408@gmail.com> <CAOj+MMGKN9drVzJgrE6WVkF6k43Vqe6TNwK9VpHpFbJTafKUdA@mail.gmail.com> <880939EA-32A0-4869-A272-0E7416DED534@gmail.com> <16253F7987E4F346823E305D08F9115AAB8D7E66@nkgeml514-mbx.china.huawei.com>
In-Reply-To: <16253F7987E4F346823E305D08F9115AAB8D7E66@nkgeml514-mbx.china.huawei.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [131.228.2.20]
user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
x-clientproxiedby: PR0P264CA0071.FRAP264.PROD.OUTLOOK.COM (2603:10a6:100:1d::35) To DB7PR07MB5483.eurprd07.prod.outlook.com (2603:10a6:10:32::17)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=martin.vigoureux@nokia.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d6accce0-1355-42b7-83d9-08d6faeb5a37
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:DB7PR07MB5307;
x-ms-traffictypediagnostic: DB7PR07MB5307:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <DB7PR07MB5307FEA8CA2ECA80E4B1E38F8CFD0@DB7PR07MB5307.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 008184426E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(39860400002)(376002)(366004)(136003)(396003)(199004)(51914003)(189003)(6486002)(110136005)(66946007)(2501003)(6246003)(66556008)(73956011)(31696002)(186003)(8936002)(386003)(316002)(5660300002)(99286004)(53936002)(81156014)(6436002)(81166006)(64756008)(11346002)(2906002)(6506007)(8676002)(66574012)(14454004)(58126008)(66446008)(3846002)(76176011)(6116002)(54906003)(6306002)(31686004)(65956001)(229853002)(65806001)(446003)(66066001)(486006)(86362001)(68736007)(66476007)(64126003)(71200400001)(52116002)(36756003)(476003)(71190400001)(65826007)(6512007)(7736002)(26005)(305945005)(4326008)(966005)(14444005)(102836004)(256004)(478600001)(2616005)(25786009)(518174003); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR07MB5307; H:DB7PR07MB5483.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 6R01YxpVNCglN7QpJRKzFWsQkW+2ZVxkFxceXkdGPyvlD4b9C0vmCuHTUBf/bFQqP/viPY0EK3Qk/ELcfMhwhVCcTe2x265qEtbtQPsB9FTN5Qp2lf0BIehBPYtSxtJHhrdpXHnsvtXtRYrYtPVoaNABPjgoVJC0uVOjzCh7qNq1TF2+bLW4vH8l5MoCzc1/5NLrXSW8FtUSs/O2kQu831SHaburcevpWZUN2R80hsdYgG7gGMueTlczk33QIXuIgaFOE5UPdV51kLZ2J8WfCp1mNzDYRPc0r6Zwp6sgl3guA9nIWoSLZ/dMEB1nOspTTpfdHdLGQdSsN7eM3ymyQZidxRt+Z+Ld0MYhZRYk/YvLcKs2vERsiPM409R6/jkfX/ucqU2uH0zuy7BGFNbLftN/CNPZkre2mk4d7sK1Z88=
Content-Type: text/plain; charset="utf-8"
Content-ID: <18844DE5CE4B0D418AA4D1FA84DC7D2F@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d6accce0-1355-42b7-83d9-08d6faeb5a37
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Jun 2019 10:36:45.9698 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: martin.vigoureux@nokia.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB5307
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/j9_nm0G2Q1BUMZPC4PrTesvb3kw>
Subject: Re: [Softwires] [Idr] [bess] Regarding the Next Hop Network Address coding for IPv4 VPN over IPv6 Core in RFC5549
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2019 10:36:54 -0000

since we are discussing that topic,

maybe the WG would like to reach a conclusion on how to treat that erratum:
http://www.rfc-editor.org/errata/eid5738

Thanks
-m

Le 2019-06-27 à 11:15, Xiejingrong a écrit :
> Thanks for the RFC historical lessons.
> 
> --there was historically some assumption that next hop must be of the 
> same AF as prefix.
> 
> --RFC 2858 says that Next Hop field should match AFI. On the other hand, 
> RFC 4760 says that Next Hop Field should match combination of AFI/SAFI.
> 
> --authors of RFC 4364 were trying to make it consistent with 4760.
> 
> --Also, drafts of RFC 4364 and RFC 4760 were being developed practically 
> at the same time period.
> 
> The problem is clear, the nexthop field has been inconsistent between 
> different L3VPN/MVPN scenarios and different implementations in the long 
> history.
> 
> <draft-dawra-bess-srv6-services-00> is the latest draft, but it has 
> different nexthop in section 3.1 to 3.4, in the year 2019.
> 
> Back to my suggestion: implementation should interpret nexthop RD+IPv4 
> and nexthop IPv4 the same, and interpret nexthop RD+IPv6 and nexthop 
> IPv6 the same.
> 
> I think it may be helpful for <draft-dawra-bess-srv6-services-00> to add 
> the above text, and update RFC4364/4659/4760/5549, to eliminate the 
> worries about interoperation. ----is there any worries about 
> interoperation ?
> 
> Thanks
> 
> Jingrong
> 
> *From:*Alexander Okonnikov [mailto:alexander.okonnikov@gmail.com]
> *Sent:* Wednesday, June 26, 2019 9:38 PM
> *To:* Robert Raszuk <robert@raszuk.net>
> *Cc:* UTTARO, JAMES <ju1738@att.com>om>; Xiejingrong 
> <xiejingrong@huawei.com>om>; softwires@ietf.org; idr@ietf.org; 
> ian.farrer@telekom.de; bess@ietf.org; ianfarrer@gmx.com
> *Subject:* Re: [Idr] [bess] [Softwires] Regarding the Next Hop Network 
> Address coding for IPv4 VPN over IPv6 Core in RFC5549
> 
> Hi Robert,
> 
> Sorry, I was not so precise :-) Of course, RD part in Next Hop is not 
> copied from RD of NLRI, but zeroed. I was trying to explain why Next Hop 
> field in RFC 4364 and RFC 4659 has format RD:IP (VPNvX address) rather 
> than just IP.
> 
> Thank you!
> 
> 
> 
> 
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>