Re: New Version Notification for draft-petrescu-6man-ll-prefix-len-17.txt

tom petch <ietfc@btconnect.com> Tue, 14 May 2019 09:28 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D15F120049 for <ipv6@ietfa.amsl.com>; Tue, 14 May 2019 02:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level:
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RATWARE_MS_HASH=2.148, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.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 6EQ5MqWy7J-J for <ipv6@ietfa.amsl.com>; Tue, 14 May 2019 02:28:02 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on072d.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe1e::72d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CCEB120043 for <ipv6@ietf.org>; Tue, 14 May 2019 02:28:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2fOQ/IrSQc9vD59xLvF4rkwdZMZ/lV1Qn3EFNsZvvME=; b=ePRpYyHg0uafP9CpFet2qjbyxBCzpsbUsPyANVlnkYl0LAeDpBff62j70BzXaDzU4qPhYPwYEALiAPoO9nRQtujuYv5Sl7VHK694JBNOaZMHld2fpaTdoYvic2gGrNOa1U4z6IKImDUI3k5J78E10zmbCsD0k6T9hjy1GHCWYNA=
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com (10.175.242.156) by VI1PR07MB4973.eurprd07.prod.outlook.com (20.178.8.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1900.13; Tue, 14 May 2019 09:27:58 +0000
Received: from VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::41a4:68a9:d620:d42b]) by VI1PR07MB3118.eurprd07.prod.outlook.com ([fe80::41a4:68a9:d620:d42b%3]) with mapi id 15.20.1900.010; Tue, 14 May 2019 09:27:58 +0000
From: tom petch <ietfc@btconnect.com>
To: "hayabusagsm@gmail.com" <hayabusagsm@gmail.com>, "sthaug@nethelp.no" <sthaug@nethelp.no>
CC: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: New Version Notification for draft-petrescu-6man-ll-prefix-len-17.txt
Thread-Topic: New Version Notification for draft-petrescu-6man-ll-prefix-len-17.txt
Thread-Index: AQHVCjdRJUefvAov1kiHQ9PpvZGL0g==
Date: Tue, 14 May 2019 09:27:58 +0000
Message-ID: <026d01d50a36$cb95c6c0$4001a8c0@gateway.2wire.net>
References: <3aca6800-8b3e-8a0e-eacb-2cd8eceddbb9@gmail.com> <20190513.115657.485273190.sthaug@nethelp.no> <CC44D89A-9002-4807-B43D-408B6B81D315@gmail.com> <20190513.163247.474361422.sthaug@nethelp.no>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: LO2P265CA0345.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:d::21) To VI1PR07MB3118.eurprd07.prod.outlook.com (2603:10a6:802:20::28)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-mailer: Microsoft Outlook Express 6.00.2800.1106
x-originating-ip: [86.139.215.234]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 259aee55-c2d4-4654-4acb-08d6d84e73be
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:VI1PR07MB4973;
x-ms-traffictypediagnostic: VI1PR07MB4973:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <VI1PR07MB4973161A835F7E9E13564D7FA0080@VI1PR07MB4973.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 0037FD6480
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(136003)(366004)(376002)(396003)(39860400002)(189003)(199004)(13464003)(486006)(50226002)(2501003)(14496001)(1556002)(71190400001)(4720700003)(6116002)(84392002)(76176011)(71200400001)(305945005)(86152003)(476003)(81816011)(7736002)(81686011)(44736005)(6486002)(52116002)(5660300002)(229853002)(6436002)(3846002)(2906002)(14454004)(99286004)(15650500001)(6506007)(386003)(25786009)(53936002)(186003)(6246003)(102836004)(66066001)(26005)(61296003)(68736007)(6512007)(9686003)(8676002)(966005)(62236002)(81156014)(44716002)(81166006)(6306002)(66556008)(64756008)(66446008)(86362001)(66476007)(66946007)(8936002)(256004)(14444005)(478600001)(45080400002)(110136005)(66574012)(316002)(73956011)(4326008)(446003)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB4973; H:VI1PR07MB3118.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0;
received-spf: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: HBAUquegop3ZjCnjOjR5i32+mMPAyb6Cj3zX9md2Lp/yDLShOM8kjW6ktVyU/s2gs8F5JfBt+el1vlT25qcSEk081/NJFVRse3ELPtCMbB4emvw84DrTgGKZegue1bE33+TQHKQRS8s2yaiNXuEZVTm6waU4rntVmkx0yj+rx0ZaNm497HO1NvCsaXjPtXo5rNG92xCUBBV7LwlqMR7BQqLcr9mB0Qxn/0GSH7ABQ+hnaLx90OXrrPeg/UaN0wDqZGYrqKbaqxFSkgA6/ceoifbjhyrUwhz5B9HNhxq9rFv6PGHU8XkVMMos0mUtEBGfkX6Ruf7XEbktdBkdtrAEVYfgduy3AHMZE6BgWg0pUyt/tRiVH+UkEK0Zx3XskB/ysEv+V55I8L/CkYlMC+bCq2nbjQI1V2r7TZ3sIyS9qAs=
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8620D14A91BFC5499919F01430C098E1@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 259aee55-c2d4-4654-4acb-08d6d84e73be
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 May 2019 09:27:58.4131 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB4973
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/f_5QwjzOI7_2rbP73uPnFt6_1HA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2019 09:28:06 -0000

----- Original Message -----
From: <sthaug@nethelp.no>
Sent: Monday, May 13, 2019 3:32 PM

> > I agree that we need an IPv6 router id 128 bit expanded field
>
> Why? I really doubt you're planning more than 2^32 routers in your
> OSPF infrastructure.
>
> > and even now with the IPv6-only flag draft of which Microsoft and
maybe other vendors are getting on board as major players that
enterprises can definitely deploy managed networks to IPv6 only in the
access side and use 6to4 nat 6to4 dns and 6to4 proxy for internal and
external IPv4 resource access.
>
> There is no connection between IPv6-only and 32 bit OSPF router ID, as
> far as I can see. A 32 bit OSPF router ID won't prevent you from going
> IPv6-only.

Absolutely.  RFC8294 defines router-id as
"A 32-bit number in the dotted-quad format assigned to each
          router.
(note: dotted quad - a convenient way of writing, reading, speaking ...
a 32 bit number which carries no semantic overtones).

MPLS, traffic engineering and such-like require a routable IPv4 or IPv6
(or both) address and those are specified separately and are commonly
referred to as te-rid or Traffic Engineering Router-ID - see for example
draft-ietf-ospf-yang

So I see no problem that was not solved many years ago.

Tom Petch

> Steinar Haug, AS2116
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------