IETF Logo Mail Archive

Re: [Idr] Can the Network Address of Next Hop be an IPv4 address of the egress PE?

"Rajiv Asati (rajiva)" <rajiva@cisco.com> Thu, 31 January 2019 08:43 UTC

Return-Path: <rajiva@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFED5130E9B; Thu, 31 Jan 2019 00:43:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.642
X-Spam-Level:
X-Spam-Status: No, score=-14.642 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, 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, 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
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 Rzs-jeloba4S; Thu, 31 Jan 2019 00:43:18 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0827F130E99; Thu, 31 Jan 2019 00:43:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6652; q=dns/txt; s=iport; t=1548924198; x=1550133798; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=jWIwmNXyf9ygBNqD9Z124OmJkNWhwJwL6+KPGi07GVE=; b=B8s4/LK9tCmwyl1LbwrsBhFbYEa0pz6Nb4qKyB0ONj9+C00RNhYcU1SG COoT2PSmMTCOKF/LJx02wfgBVF/sutueglJKz3b7TKZz7TmOYgMCMdXQ/ 6E+rGTqE3VPboHpUSirW7WDxQO68gPKIny1dEsh1aTqjYIhWqQZK0PEgL 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAADJs1Jc/4ENJK1jGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ12Z4EDJ4QDiBqNW5JEhW+BewsBARgBCoRJAheCciI0CQ0BAwEBAgEBAm0cDIVLAgEDAQEhCkELEAIBCD8DAgICJQsUEQEBBA4FgyIBgR1kD6xggS+KMAWMQBeBQD+BOAwTgh4ugx4BAQIBhGcxgiYCkAqSVwkChy2LBhmBa4h5h1iPTYwAAhEUgScfOIFWcBU7KgGCQYIsEhOITIU/QTEBkAwBAQ
X-IronPort-AV: E=Sophos;i="5.56,543,1539648000"; d="scan'208,217";a="500884086"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Jan 2019 08:43:16 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x0V8hGvY028428 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 31 Jan 2019 08:43:16 GMT
Received: from xch-aln-005.cisco.com (173.36.7.15) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 31 Jan 2019 02:43:16 -0600
Received: from xch-aln-005.cisco.com ([173.36.7.15]) by XCH-ALN-005.cisco.com ([173.36.7.15]) with mapi id 15.00.1395.000; Thu, 31 Jan 2019 02:43:16 -0600
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "Chengli (Cheng Li)" <chengli13@huawei.com>
CC: "draft-dawra-idr-srv6-vpn@ietf.org" <draft-dawra-idr-srv6-vpn@ietf.org>, "idr@ietf. org" <idr@ietf.org>
Thread-Topic: [Idr] Can the Network Address of Next Hop be an IPv4 address of the egress PE?
Thread-Index: AdS5Pf6+A05CkmTOR2SM9j+zirq4nQANR2yA
Date: Thu, 31 Jan 2019 08:43:16 +0000
Message-ID: <45BDA2DD-A1EF-4533-81BD-A2894B39D1A4@cisco.com>
References: <C7C2E1C43D652C4E9E49FE7517C236CB01ACA4DD@dggeml529-mbx.china.huawei.com>
In-Reply-To: <C7C2E1C43D652C4E9E49FE7517C236CB01ACA4DD@dggeml529-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_45BDA2DDA1EF453381BDA2894B39D1A4ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: alln-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/fu9K8Yq790meSsztA9_XzCYIjVg>
Subject: Re: [Idr] Can the Network Address of Next Hop be an IPv4 address of the egress PE?
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2019 08:43:20 -0000

Short answer - no (and IPv4, if existed, must not be used). The idea with SRv6 is to use IPv6 for underlay.

Cheers,
Rajiv Asati



On Jan 31, 2019, at 9:24 AM, Chengli (Cheng Li) <chengli13@huawei.com<mailto:chengli13@huawei.com>> wrote:

Hi Authors,

I have a question when I read  https://tools.ietf.org/html/draft-dawra-idr-srv6-vpn-05#section-3.1 : Network Address of Next Hop = IPv6 address of the egress PE.

If the network is a V4/V6 dual stack network, can the Network Address of Next Hop be an IPv4 address of the egress PE?

Thanks,
Cheng







_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email