Re: [Lsr] Enhancements on encoding of router IDs and DR IDs
Huaimo Chen <hchen@futurewei.com> Sun, 26 May 2019 03:30 UTC
Return-Path: <hchen@futurewei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2A1C12008C for <lsr@ietfa.amsl.com>; Sat, 25 May 2019 20:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_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=futurewei.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 igGnZjGddbtb for <lsr@ietfa.amsl.com>; Sat, 25 May 2019 20:30:36 -0700 (PDT)
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (mail-eopbgr710098.outbound.protection.outlook.com [40.107.71.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D12C412002F for <lsr@ietf.org>; Sat, 25 May 2019 20:30:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=05ym0pViSP8VDKmSDxUVmAhCVObr8f45haeW5cEqOVY=; b=suJMlXWXPNva+Uqvcs+1MoZ4O4pkORt/6CMf6+US0THR7TAzySbOb3n4Q5z+Qen5fJNAWuqqaZiClvBonta+l8jOIn0bqtqjypRvKtoq3gIDFaLoWWnQeuuk5ArOxW3EnpVi+sRTuQip30fycs3oMQNyqrbXGhB18yoFW6+22Zo=
Received: from MN2PR13MB3470.namprd13.prod.outlook.com (10.255.237.83) by MN2PR13MB3150.namprd13.prod.outlook.com (20.179.150.84) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.13; Sun, 26 May 2019 03:30:30 +0000
Received: from MN2PR13MB3470.namprd13.prod.outlook.com ([fe80::2528:ed2a:12eb:38df]) by MN2PR13MB3470.namprd13.prod.outlook.com ([fe80::2528:ed2a:12eb:38df%4]) with mapi id 15.20.1922.016; Sun, 26 May 2019 03:30:30 +0000
From: Huaimo Chen <hchen@futurewei.com>
To: Peter Psenak <ppsenak@cisco.com>, Tony Li <tony.li@tony.li>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] Enhancements on encoding of router IDs and DR IDs
Thread-Index: AQHVEZagizwHqkR6U0+FYJpmt4hA+aZ6BQCAgAK8/5A=
Date: Sun, 26 May 2019 03:30:30 +0000
Message-ID: <MN2PR13MB3470891CE38D8A432F921A76A31C0@MN2PR13MB3470.namprd13.prod.outlook.com>
References: <MN2PR13MB34708672AA4CC7BB2AF61269A3010@MN2PR13MB3470.namprd13.prod.outlook.com>, <20066aa5-f45b-26a9-3ae5-fbc9af16931d@cisco.com>
In-Reply-To: <20066aa5-f45b-26a9-3ae5-fbc9af16931d@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=hchen@futurewei.com;
x-originating-ip: [73.114.233.24]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 90f232ea-8907-438f-2ce1-08d6e18a8137
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR13MB3150;
x-ms-traffictypediagnostic: MN2PR13MB3150:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR13MB3150152065BFEB256FDA69F8A31C0@MN2PR13MB3150.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0049B3F387
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(136003)(39830400003)(376002)(366004)(346002)(51914003)(189003)(199004)(66446008)(73956011)(64756008)(6606003)(53936002)(66946007)(66476007)(7736002)(76116006)(66556008)(966005)(229853002)(91956017)(236005)(606006)(2906002)(1015004)(561944003)(33656002)(3846002)(6116002)(9686003)(8676002)(6436002)(14454004)(55016002)(54896002)(6306002)(71200400001)(81156014)(81166006)(66574012)(8936002)(71190400001)(478600001)(45080400002)(52536014)(102836004)(486006)(186003)(11346002)(446003)(6506007)(53546011)(476003)(99286004)(74316002)(25786009)(76176011)(7696005)(86362001)(316002)(19627405001)(68736007)(256004)(5024004)(2501003)(110136005)(6246003)(26005)(66066001)(5660300002); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB3150; H:MN2PR13MB3470.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: qsihRGK0zmsNilwCtOwyLCHx3Tuz7hdyHFOIpXcTenOUOz4N3naKPL+fRqrovXi5t/9+q6MHAswr5Y2JxCs5M9Sao3nNPGLhcUai/n6WG3ck6NR2y50YTVcJ6rtu0IWhrTulwZzGfEPidSsKt47/e5wiSQuWcs7gUh9VMlk8esDo7BpBxHdIQ5J8LctUX6a6JzbktDomCA7mhG1R+tcak672baLs2/rdgDJvrbP4IvQqoe/4CA/pyBGPa46oYC56Cv9Y7nun2ojtScaX9UsljZNzJVGlLdMTdD+5FSs/2ljkckcFZ2HYqww0tIdvpzJ2zjPE7KFXuj8yokLgR1uzgv2xIRZUVI/bRSIyocDRUV1cUcr4VHy4v294xVrOOezEcbB5/7C94hy/KM14IfEZ7AasEQrbEwhkHzw4PfQ/xeY=
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB3470891CE38D8A432F921A76A31C0MN2PR13MB3470namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 90f232ea-8907-438f-2ce1-08d6e18a8137
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 May 2019 03:30:30.6685 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: hchen@futurewei.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3150
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/Xwq7kaapZxoJ0qLDifW_0d_vSWg>
Subject: Re: [Lsr] Enhancements on encoding of router IDs and DR IDs
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 May 2019 03:30:39 -0000
Hi Peter,
Thank you very much.
After it is included in draft-ietf-lsr-dynamic-flooding, we can work together to reduce the side effect.
Best Regards,
Huaimo
________________________________
From: Peter Psenak <ppsenak@cisco.com>
Sent: Friday, May 24, 2019 5:35 AM
To: Huaimo Chen; Tony Li; lsr@ietf.org
Subject: Re: [Lsr] Enhancements on encoding of router IDs and DR IDs
Hi Huaimo,
thanks for the suggestion, I think it's good one to include.
One side effect of your proposal is that when the new ID or DR ID is
inserted, it may cause other IDs/DR IDs to change their index, as you
can not assume you can simply add to the end of the list anymore.
thanks,
Peter
On 23/05/2019 20:47 , Huaimo Chen wrote:
> Hi Tony,
>
>
> Enhancements on encoding the IDs are described below for
> discussions. A .pdf file is attached in the case that the formats below
> are messed up.
>
>
> Currently for OSPFv2, OSPFv2 Area Router IDs TLVs are used to represent
> a sequence of router IDs or DR IDs (addresses). Each of IDs is encoded
> as an OSPFv2 Router IDs TLV Entry of 8 bytes.
>
> 0 1 2 3
>
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | Conn Type | Reserved |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | Originating Router ID/DR Address (4 bytes) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> (Current) OSPFv2 Router IDs TLV Entry
>
>
>
> To represent N router IDs or DR addresses, we need N entries, which
> occupies 8*N bytes in the OSPFv2 Area Router IDs TLVs. Each entry
> represents just only one router ID or DR address.
>
>
>
> An enhancement below is to allow one entry to represent a number of
> router IDs or a number of DR addresses. This can be achieved by using
> two bytes of the Reserved field to indicate the number M of router IDs
> or a number of DR addresses contained in the entry. The value of the
> two bytes can be the number of IDs/Addresses (i.e., M) or the number of
> octets used (i.e., 4*M). The former is preferred.
>
>
>
> 0 1 2 3
>
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | Conn Type | NumberOfIDs (M) | Reserved |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | 1st Originating Router ID/DR Address (4 bytes) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | 2nd Originating Router ID/DR Address (4 bytes) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | |
>
> ~ . . . . . . ~
>
> | |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | M-th Originating Router ID/DR Address (4 bytes) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> (Enhanced) OSPFv2 Router IDs TLV Entry
>
>
>
> To represent N router IDs or N DR addresses using the enhanced entry, we
> need just one or a few entries. Using X entries occupies 4*(N + X) bytes
> in the OSPFv2 Area Router IDs TLVs.
>
>
>
> Consider the case where there are 1000 routers in an area. To represent
> 1000 router IDs,
>
> Using the current OSPFv2 Router IDs TLV Entries occupies 8*1000 = 8000
> bytes;
>
> Using the enhanced OSPFv2 Router IDs TLV Entries occupies 4*(1000 + 1) =
> 4004 bytes.
>
> 8000/4004 = 1..998. The saving on space is about 50% in this case.
>
>
>
> Similarly for OSPFv3, OSPFv3 Area Router IDs TLVs are used to represent
> a sequence of router IDs or DR IDs. Each of router IDs is encoded as an
> OSPFv3 Router IDs TLV Entry of 8 bytes. Each of DR IDs is encoded as an
> OSPFv3 Router IDs TLV Entry of 12 bytes.
>
>
>
> 0 1 2 3
>
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | Conn Type | Reserved |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | Originating Router ID (always present) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | Interface ID (present for DRs) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> (Current) OSPFv3 Router IDs TLV Entry
>
>
>
> An enhancement below is to allow one entry to represent a number of
> router IDs or a number of DR IDs. This can be achieved by using two
> bytes of the Reserved field to indicate the number M of router IDs or a
> number of DR IDs contained in the entry. The value of the two bytes can
> be the number of IDs (i.e., M) or the number of octets used (i.e., 4*M
> for M router IDs or 8*M for M DR IDs). The former is preferred.
>
>
>
> 0 1 2 3
>
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | Conn Type | NumberOfIDs (M) | Reserved |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | 1st Originating Router ID (always present) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | 1st Interface ID (present for DRs) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | 2nd Originating Router ID (always present) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | 2nd Interface ID (present for DRs) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | |
>
> ~ . . . . .. . ~
>
> | |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | M-th Originating Router ID (always present) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | M-th Interface ID (present for DRs) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> (Enhanced) OSPFv3 Router IDs TLV Entry
>
>
>
>
> Best Regards,
>
> Huaimo
>
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Flsr&data=02%7C01%7Chchen%40futurewei.com%7Ca64e7494268f40814a5208d6e02b3cbe%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C636942873655794273&sdata=96k2VMi7zhftIeoZFfcHJpsyX2UdII6R2LbOvLpBFIY%3D&reserved=0
>
- [Lsr] Enhancements on encoding of router IDs and … Huaimo Chen
- Re: [Lsr] Enhancements on encoding of router IDs … Peter Psenak
- Re: [Lsr] Enhancements on encoding of router IDs … Huaimo Chen