Re: [Sidrops] draft-ietf-sidrops-8210bis flag bits

Randy Bush <randy@psg.com> Sat, 07 May 2022 19:13 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37D7EC147930 for <sidrops@ietfa.amsl.com>; Sat, 7 May 2022 12:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lxe0X-skgHrv for <sidrops@ietfa.amsl.com>; Sat, 7 May 2022 12:13:53 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C14B4C14F728 for <sidrops@ietf.org>; Sat, 7 May 2022 12:13:53 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.93) (envelope-from <randy@psg.com>) id 1nnPsF-0005VL-0L; Sat, 07 May 2022 19:13:51 +0000
Date: Sat, 07 May 2022 12:13:50 -0700
Message-ID: <m25ymhnok1.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
Cc: SIDR Operations WG <sidrops@ietf.org>, Warren Kumari <warren@kumari.net>
In-Reply-To: <CAL9jLaZhUJ5OT+ErkKp17jdrCWdUN6_JQeMp5xQmG5hHZbSADw@mail.gmail.com>
References: <m2wnf3r5rs.wl-randy@psg.com> <CAL9jLaZhUJ5OT+ErkKp17jdrCWdUN6_JQeMp5xQmG5hHZbSADw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/3gCFV9yj5dHxljFP8ksNTLe1w8M>
Subject: Re: [Sidrops] draft-ietf-sidrops-8210bis flag bits
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 May 2022 19:13:54 -0000

>> alternatively, we could have an ASPA4 and ASPA6.  parallel
>> construction is nice.  but the actual PDUs would be *identical*
>> except for the PDU Type.
>
> it seems, to me, that having the parallel pdus is ok. it might be nice
> to avoid 2x pdu types, but we (I think) certainly do not want to
> change how flag bits are defined suddenly.

the choice is not that extreme.  as the AFI flag bit is really only
needed for the new ASPA PDU, i suggested a second and separate flag
field, see AFI Flag below

>> 0          8          16         24        31
>> .-------------------------------------------.
>> | Protocol |   PDU    |                     |
>> | Version  |   Type   |        zero         |
>> |    2     |    11    |                     |
>> +-------------------------------------------+
>> |                                           |
>> |                 Length                    |
>> |                                           |
>> +-------------------------------------------+
>> |          |          |                     |
>> |  Flags   | AFI Flag |  Provider AS Count  |
>> |          |          |                     |
>> +-------------------------------------------+
>> |                                           |
>> |    Customer Autonomous System Number      |
>> |                                           |
>> +-------------------------------------------+
>> |                                           |
>> |    Provider Autonomous System Numbers     |
>> |                                           |
>> ~-------------------------------------------~

unless someone comes up with a better scheme, i will do this in the next
rev, after the IMC dreadline in a couple of weeks.  there were a lot of
good directorate reviews.

randy