Re: [dhcwg] Barry Leiba's No Objection on draft-ietf-dhc-slap-quadrant-09: (with COMMENT)

Barry Leiba <barryleiba@computer.org> Mon, 03 August 2020 16:45 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB103A0F45; Mon, 3 Aug 2020 09:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 FBaNHe5ekn4y; Mon, 3 Aug 2020 09:45:38 -0700 (PDT)
Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (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 DC8C93A0F44; Mon, 3 Aug 2020 09:45:37 -0700 (PDT)
Received: by mail-io1-f47.google.com with SMTP id q75so31038524iod.1; Mon, 03 Aug 2020 09:45:37 -0700 (PDT)
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:content-transfer-encoding; bh=vctxTBah88xcdkURxt4s80LMvRchKfpbKvSfq3r8gyI=; b=CtNIZSV5iXcOYIAteFfqgjxMj4quKDjACCyZc1GwLT2PGeIiF3DIJ4ZTq+Zhv5Okiu 1Xri4VkRMLCPiin9+z3wyQMMj5eMnaA50Uw0YfMewulN/P/tnMJHKX1X8Tjjubqmg44H FloJXssz/FA/EkWI2jzNoL8R+jV1+HgPGRfAxONGLM6Eo1Xbpu1i5hRzOGuOH+yn+e0D OVdvUoZeIJqStUBdnMq0m+Z9NJjZfklO5rqctgs2vlefzNV5AGD/DmcjIdKJuyumU2J+ YaF5yzyQRjMPBOOoWQ8OTwxtCLDG5J/OALU2WiMJFKSIqZhyF7nXbk57m1tE7ITwQ6yK /9lQ==
X-Gm-Message-State: AOAM530zP4SgncaPuzCLX6QLt7DGj8ze2Z3ttnpPVY1vxeYRgAEsPQKf UaL8qaXhk+Pygk1FMHZTr04nL//BwHFidOZfzqE=
X-Google-Smtp-Source: ABdhPJzU9OHwaGSQeRuyzgTeEHXJ0dLI31ZErJI9krHXZ0kZ11Q/g2Ol9+K4r/mZT+IfHs0vNJarizXoh/TjYvxr1IM=
X-Received: by 2002:a6b:9042:: with SMTP id s63mr710294iod.195.1596473136933; Mon, 03 Aug 2020 09:45:36 -0700 (PDT)
MIME-Version: 1.0
References: <159166707503.4308.11011951864784667729@ietfa.amsl.com> <CALypLp_J_k3qFMaUteQvq6coEY-ZFwkbD1YB82W0GEDSKpT4VQ@mail.gmail.com> <CALaySJJ8TXBLy6iJZpxiN-LuVFejmJh4B0cjtPotwhwBFOWiBQ@mail.gmail.com> <CALypLp8wczjvJq+8Akxg1mRyzeDE2HO3Bzuf6Z9-6V2OrgHhtQ@mail.gmail.com>
In-Reply-To: <CALypLp8wczjvJq+8Akxg1mRyzeDE2HO3Bzuf6Z9-6V2OrgHhtQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 3 Aug 2020 12:45:25 -0400
Message-ID: <CALaySJJXWudPNdD87NShTHhfk35w8mk6Bd-dBGKu_o-JMSXE0w@mail.gmail.com>
To: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
Cc: The IESG <iesg@ietf.org>, draft-ietf-dhc-slap-quadrant@ietf.org, dhc-chairs@ietf.org, dhcwg <dhcwg@ietf.org>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>, Ian Farrer <ianfarrer@gmx.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/2Ga9LFO9byuN1H4DXMswfIMPOY8>
Subject: Re: [dhcwg] Barry Leiba's No Objection on draft-ietf-dhc-slap-quadrant-09: (with COMMENT)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Aug 2020 16:45:39 -0000

The new text looks great; thanks!

Barry

On Mon, Aug 3, 2020 at 12:26 PM CARLOS JESUS BERNARDOS CANO
<cjbc@it.uc3m.es> wrote:
>
> Hi Barry,
>
> Thanks! Please see inline below.
>
> On Fri, Jul 31, 2020 at 9:42 PM Barry Leiba <barryleiba@computer.org> wrote:
>>
>> Thanks for the reply, Carlos.  Just responding to the two items for
>> which there are questions -- and keep in mind that my comments are
>> suggestions, and that you should do as you think best.
>>
>> >>    o  Quadrant "Reserved for future use" where MAC addresses may be
>> >>
>> >> Nit: remove “where”.
>> >
>> > [Carlos] Why should I remove it? Current text reads:
>> >
>> >    o  SLAP Quadrant 10 is "Reserved for future use" where MAC addresses
>> >       may be assigned using new methods yet to be defined, or until then
>> >       by an administrator as in the AAI quadrant.  For 48-bit MAC
>> >       addresses, 44 bits would be available.
>>
>> If you've changed the list text this comment might not apply any more,
>> but I suggested removing "where" because it makes that item different
>> from all the others in the list.  In -09, the list looks like this:
>>
>>    o  Quadrant "Extended Local Identifier" (ELI) MAC addresses are
>>       assigned based on a Company ID (CID)
>>
>>    o  Quadrant "Standard Assigned Identifier" (SAI) MAC addresses are
>>       assigned based on a protocol specified in an IEEE 802 standard.
>>
>>    o  Quadrant "Administratively Assigned Identifier" (AAI) MAC
>>       addresses are assigned locally by an administrator.
>>
>>    o  Quadrant "Reserved for future use" where MAC addresses may be
>>       assigned using new methods yet to be defined
>>
>> Why does the last one have "where", and the first three don't?  The
>> nit I noted was just the lack of parallelism, that's all.
>
>
> [Carlos] Current text (in -10 to be submitted) is the following:
>
> -8-<-
>    o  In SLAP Quadrant 01, "Extended Local Identifier" (ELI) MAC
>       addresses are assigned based on a 24-bit Company ID (CID),
>       assigned by the IEEE Registration Authority (RA).  The remaining
>       bits are specified as an extension by the CID assignee or by a
>       protocol designated by the CID assignee.
>
>    o  In SLAP Quadrant 11, "Standard Assigned Identifier" (SAI) MAC
>       addresses are assigned based on a protocol specified in an IEEE
>       802 standard.  For 48-bit MAC addresses, 44 bits are available.
>       Multiple protocols for assigning SAIs may be specified in IEEE
>       standards.  Coexistence of multiple protocols may be supported by
>       limiting the subspace available for assignment by each protocol.
>
>    o  In SLAP Quadrant 00, "Administratively Assigned Identifier" (AAI)
>       MAC addresses are assigned locally by an administrator.  Multicast
>       IPv6 packets use a destination address starting in 33-33, so AAI
>       addresses in that range should not be assigned.  For 48-bit MAC
>       addresses, 44 bits are available.
>
>    o  SLAP Quadrant 10 is "Reserved for future use" where MAC addresses
>       may be assigned using new methods yet to be defined, or until then
>       by an administrator as in the AAI quadrant.  For 48-bit MAC
>       addresses, 44 bits would be available.
> -8-<-
>
> The last one is a bit different because it is the quadrant that is reserved for future use.
>
>>
>> >> — Section 4.1 —
>> >>
>> >>       The client SHOULD NOT pick a server that does not
>> >>        advertise an address in the requested quadrant.
>> >>
>> >> This SHOULD NOT doesn’t make sense to me.  Why would it?  What would be an
>> >> informed reason to pick one that doesn’t have what it wants?  Is there a reason
>> >> not to just say, “The client will pick a server that advertises an address in
>> >> the quadrant the client requested,” without using BCP 14 key words?
>> >>
>> > [Carlos] We wrote in that way to leave freedom for cases in which maybe there are no
>> > servers that have what the client wants (or better, prefers) and still allow the client to
>> > get an address allocation from a server.
>>
>> It might be good, then, to explain that briefly: the text that's there
>> simply says what I quote above, with no explanation, and says nothing
>> about what the client might want or prefer.  So when I read it, I say
>> to myself, "If I ask for an address in a specific quadrant, why would
>> I pick a server that doesn't have one?"  Maybe it's just as simple as,
>> "The client will pick a server that advertises an address in the
>> quadrant the client requested, unless no server advertises one."  Or
>> maybe the "SHOULD NOT" is fine with a brief explanation.  Or maybe
>> readers will just understand this, and I'm blowing smoke: as I said,
>> do as you think best.
>
>
> [Carlos] OK, I see your point. I still think I'm going to keep the current text.
>
> Thanks a lot!
>
> Carlos
>
>>
>>
>> Barry