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

Robert Raszuk <robert@raszuk.net> Wed, 26 June 2019 11:53 UTC

Return-Path: <robert@raszuk.net>
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 CDEC61204AA for <softwires@ietfa.amsl.com>; Wed, 26 Jun 2019 04:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 3qQJHiYDG07v for <softwires@ietfa.amsl.com>; Wed, 26 Jun 2019 04:53:17 -0700 (PDT)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB9641202A1 for <softwires@ietf.org>; Wed, 26 Jun 2019 04:53:13 -0700 (PDT)
Received: by mail-qk1-x72f.google.com with SMTP id a27so1343554qkk.5 for <softwires@ietf.org>; Wed, 26 Jun 2019 04:53:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/FOQlHi6RTxWKKcVZpvLxSRYAhyXN9picfh+J0VB08w=; b=fmfYEcduNp/YS29kL2ha1bQ8E2y8y2/7fmivAdr+0Bj6QIsSNi/R/VbTuUrEc199Fv wnPlIYOpwvEGA/QJVWKe9ivfRcaJTfKkJ1uhWL9Fhco4Ot6lgBGgHCewMRumirYYByb0 vRzeft19zZnXKaHMMeYuJ8jaHlIkPo/KcyavdpVgKO7f9FRJ1BxhDUbzyP7ubCf7WM4M 7UV4nbXdbNInDkt53xhOa/Y/SXNpD2LG+YFgL2svWWwNNFUHszzxOd/fzKtkeZTN5CKU UyaCecjbHkaFy4UQGygM1fXEEkyn1ag2dYt5LDm4Ti1wLtxbDUxEdxzhQv0dKLwCUp64 GMvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/FOQlHi6RTxWKKcVZpvLxSRYAhyXN9picfh+J0VB08w=; b=h7ePBJ2Kvb3tADXKctY7PAtvVKXwhO9M4xLU5mMg9mFg6BUT3aAwa3egrvFMPDtxgh 89gT4JxUj9OqRSrQRB6I09hiKbTooz/sVvxhcgPTjAGRE0BHAj5Orof1Rh0AEJsIsJ/I zdj3TXmGKrIQhJjJImQcCJvKFNW5gDHGVQqipgSvOjes4GiTdsEDB6mQzJ/mJjks8d1q oCGHonjUQpVqv4Zv4i65R2uSPyRwLjzulBgcYqQ1viXTAeW+/8LIcHyehCAl9mxl4BEQ bbtVWsB1xolTDYflECfJ5xHhU/3F88XbM4IY6Nrp/oBMgIQnYqMNSdDGiBxKXmY7+a8Z 9UZA==
X-Gm-Message-State: APjAAAXCabg6thawfsHLgIz3Rq4HK5sWCEHrimKjmTpSBQ9VnSd+ipcj BaldAuJKphy/tMw4jw9j4jj0zrl2Py58j2tX0HX0TQ==
X-Google-Smtp-Source: APXvYqyqdVpdiwVm1zLyHyd1yJbAdlfGiaZj1Lo6ix/gzrFi34wXyZEBTqYn/xZmMvMsQC3uIoxJUpyLlb9AqFgRQXI=
X-Received: by 2002:a05:620a:1286:: with SMTP id w6mr3371993qki.219.1561549992545; Wed, 26 Jun 2019 04:53:12 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <16253F7987E4F346823E305D08F9115AAB8D61CE@nkgeml514-mbx.china.huawei.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 26 Jun 2019 13:52:59 +0200
Message-ID: <CAOj+MMGdoi1ROTmbuFu8eXWix6JfYwO1TCPUakyOEdTU01-1zA@mail.gmail.com>
To: Xiejingrong <xiejingrong@huawei.com>
Cc: "ian.farrer@telekom.de" <ian.farrer@telekom.de>, Zhuangshunwan <zhuangshunwan@huawei.com>, "ianfarrer@gmx.com" <ianfarrer@gmx.com>, "softwires@ietf.org" <softwires@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009ae128058c38b045"
Archived-At: <https://mailarchive.ietf.org/arch/msg/softwires/COR_Nz4nsZ4B6gkwHl7tfpAOA44>
Subject: Re: [Softwires] [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: Wed, 26 Jun 2019 11:53:26 -0000

All,

RD is a property of the NLRI not next hop. I am not sure where in this
thread or some spec someone came to the conclusion that next hop field
should contain an RD. RD is not useful there and should never be part of
any next hop field.

Remember RD role is to make prefix unique - that's it - no more no less.
Next hop uniqness is given by architecture and there is no need to make it
unique.

In some cases when we need to carry IPv4 address in IPv6 next hop field
(there was historically some assumption that next hop must be of the same
AF as prefix) we prepend to it numerical zeros.

Thx,
R.





On Wed, Jun 26, 2019 at 1:40 PM Xiejingrong <xiejingrong@huawei.com> wrote:

> Hi folks,
>
>
>
> I guess this is an inconsistency due to past carelessness. Is there anyone
> can tell us the history of this inconsistency ?
>
> RFC4364(VPNv4 over IPv4 network) and RFC4659(VPNv6 over IPv4 or IPv6
> network) both require to use RD+IP(v4 or v6 respectively) as nexthop.
>
> RFC5549(VPNv4/IPv4 over IPv6 network) requires to use IPv6 without RD as
> nexthop.
>
> This same question also occur in MVPN: RFC6515, which talks about MVPN6
> over IPv4/IPv6, or MVPN over IPv6, but does imply loosely to use IPv4/IPv6
> without RD as nexthop (see below).
>
>    The purpose of this document is to make clear that whenever a PE
>
>    address occurs in an MCAST-VPN route (whether in the NLRI or in an
>
>    attribute), the IP address family of that address is determined by
>
>    the length of the address (a length of 4 octets for IPv4 addresses, a
>
>    length of 16 octets for IPv6 addresses), NOT by the AFI field of the
>
>    route.
>
>
>
> My suggestion: implementation should interpret nexthop RD+IPv4 and nexthop
> IPv4 the same, and interpret nexthop RD+IPv6 and nexthop IPv6 the same.
>
> The RFC5549/SRv6-VPN/RFC6515 can keep as current shape, while interoperate
> can meet between different implementations.
>
> Need a new draft to clarify this and to give a guide on further FooService
> over FooNetwork ?
>
>
>
> Thanks
>
> Jingrong
>
>
>
> *From:* Softwires [mailto:softwires-bounces@ietf.org] *On Behalf Of *
> ian.farrer@telekom.de
> *Sent:* Tuesday, June 25, 2019 11:12 PM
> *To:* Zhuangshunwan <zhuangshunwan@huawei.com>om>; ianfarrer@gmx.com
> *Cc:* softwires@ietf.org; bess@ietf.org
> *Subject:* Re: [Softwires] Regarding the Next Hop Network Address coding
> for IPv4 VPN over IPv6 Core in RFC5549
>
>
>
> Hi Shunwan,
>
>
>
> I’ve just re-checked RFC5539, and the referenced section 3 of RFC2545 and
> I can find nothing about using VPN-IPv6 for encoding the next-hop. Section
> 3 of RFC5539 is very clear that it’s a 16-byte GU IPv6 address or 32-bytes
> with a GU and LL address.
>
>
>
> Can you point me to the text that gives you the impression that VPN-IPv6
> is correct?
>
>
>
> Note – I see that there is reported Errata on RFC5549, (not verified)
> saying that the length should be 24 or 48 to include the RD. However, as
> mentioned above, the supporting text in multiple places in the RFC and its
> references support the use of an IPv6 address (or 2) with no RD at 16 or 32
> bytes, so this does seem to be the intention of the document as written.
>
> https://www.rfc-editor.org/errata_search.php?rfc=5549
>
>
>
> Thanks,
>
> Ian
>
>
>
> *From: *Softwires <softwires-bounces@ietf.org> on behalf of Zhuangshunwan
> <zhuangshunwan@huawei.com>
> *Date: *Tuesday, 25. June 2019 at 13:18
> *To: *"ianfarrer@gmx.com" <ianfarrer@gmx.com>
> *Cc: *"softwires@ietf.org" <softwires@ietf.org>rg>, "bess@ietf.org" <
> bess@ietf.org>
> *Subject: *Re: [Softwires] Regarding the Next Hop Network Address coding
> for IPv4 VPN over IPv6 Core in RFC5549
>
>
>
> Hi Ian,
>
>
>
> Thanks for your response!
>
>
>
> The opinion I have collected is:
>
> Per RFC4634, the IPv4-VPN routes shall carry the V4 Next-hop, beginning
> with an 8-octet RD and ending with a 4-octet IPv4 address.
>
> Per RFC4659, the IPv6-VPN routes shall carry the V6 Next-hop, beginning
> with an 8-octet RD and ending with a 16-octet IPv6 address.
>
> When we start to implement the IPv4 VPN over IPv6 Core,  it is a natural
> way to encode the IPv4-VPN routes with VPN-IPv6 next-hop (i.e. beginning
> with an 8-octet RD and ending with a 16-octet IPv6 address) .
>
>
>
> I believe this is not just a minority opinion, and some of the current
> implementations are also doing this way.
>
>
>
> I hope that the WGs can give a consistent opinion on this issue and avoid
> interoperability problem in the future.
>
>
>
> Thanks,
>
> Shunwan
>
>
>
> *From:* ianfarrer@gmx.com [mailto:ianfarrer@gmx.com <ianfarrer@gmx.com>]
> *Sent:* Monday, June 24, 2019 8:08 PM
> *To:* Zhuangshunwan <zhuangshunwan@huawei.com>
> *Cc:* bess@ietf.org; softwires@ietf.org
> *Subject:* Re: [Softwires] Regarding the Next Hop Network Address coding
> for IPv4 VPN over IPv6 Core in RFC5549
>
>
>
> Hi,
>
>
>
> My reading of Section 3 of RFC5549 is that the v6 next-hop is encoded as
> an IPv6 address:
>
>
>
>    The BGP speaker receiving the advertisement MUST use the Length of
>
>    Next Hop Address field to determine which network-layer protocol the
>
>    next hop address belongs to.  When the Length of Next Hop Address
>
>    field is equal to 16 or 32, the next hop address is of type IPv6.
>
>
>
> It’s also worth noting that RFC4659 Section 2 states:
>
>
>
> A VPN-IPv6 address is a 24-octet quantity, beginning with an 8-octet
>
>    "Route Distinguisher" (RD) and ending with a 16-octet IPv6 address.
>
>
>
> So, not 16 or 32 bytes.
>
>
>
> Thanks,
>
> Ian
>
>
>
>
>
> On 22. Jun 2019, at 09:59, Zhuangshunwan <zhuangshunwan@huawei.com> wrote:
>
>
>
> Dear authors and WGs,
>
>
>
> RFC5549 Section 6.2 says:
>
>
>
> . 6.2.  IPv4 VPN over IPv6 Core
>
> .
>
> .    The extensions defined in this document may be used for support of
>
> .    IPV4 VPNs over an IPv6 backbone.  In this application, PE routers
>
> .    would advertise VPN-IPv4 NLRI in the MP_REACH_NLRI along with an IPv6
>
> .    Next Hop.
>
> .
>
> .    The MP_REACH_NLRI is encoded with:
>
> .
>
> .    o  AFI = 1
>
> .
>
> .    o  SAFI = 128
>
> .
>
> .    o  Length of Next Hop Network Address = 16 (or 32)
>
> .
>
> .    o  Network Address of Next Hop = IPv6 address of Next Hop
>
> .
>
> .    o  NLRI = IPv4-VPN routes
>
>
>
>
>
> Regarding IPv4-VPN routes, RFC4634 Section 4.3.2 says:
>
>
>
> . 4.3.2.  Route Distribution Among PEs by BGP
>
> [snip]
>
> .    When a PE router distributes a VPN-IPv4 route via BGP, it uses its
>
> .    own address as the "BGP next hop".  This address is encoded as a
>
> .    VPN-IPv4 address with an RD of 0.  ([BGP-MP] requires that the next
>
> .    hop address be in the same address family as the Network Layer
>
> .    Reachability Information (NLRI).)  It also assigns and distributes an
>
> .    MPLS label.  (Essentially, PE routers distribute not VPN-IPv4 routes,
>
> .    but Labeled VPN-IPv4 routes.  Cf. [MPLS-BGP].)  When the PE processes
>
> .    a received packet that has this label at the top of the stack, the PE
>
> .    will pop the stack, and process the packet appropriately.
>
> [snip]
>
>
>
>
>
> Question:
>
> RFC5549 defines "IPv4 VPN over IPv6 Core", When a PE router distributes a
> VPN-IPv4 route with an IPv6 Next-Hop via BGP, should the IPv6 Next-Hop be
> encoded as an VPN-IPv6 address with an RD of 0 ?
>
>
>
>
>
> Thanks,
>
> Shunwan
>
> _______________________________________________
> Softwires mailing list
> Softwires@ietf.org
> https://www.ietf.org/mailman/listinfo/softwires
>
>
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess
>