Re: [dhcwg] Benjamin Kaduk's Discuss on draft-ietf-dhc-mac-assign-07: (with DISCUSS and COMMENT)

"Bernie Volz (volz)" <volz@cisco.com> Mon, 08 June 2020 21:20 UTC

IronPort-PHdr: 9a23:qv8tZBYcXOV/GhzI3ahC6CL/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el21QaRD4Da97RJh/eF+6zjWGlV55GHvThCdZFXTBYKhI0QmBBoG8+KD0D3bZuIJyw3FchPThlpqne8N0UGHcfiIVDevy764TsbAB6qMw1zK6z8EZLTiMLi0ee09tXTbgxEiSD7b6l1KUC9rB7asY8dho4xJw==
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>, "draft-ietf-dhc-mac-assign@ietf.org" <draft-ietf-dhc-mac-assign@ietf.org>, "dhc-chairs@ietf.org" <dhc-chairs@ietf.org>, "ianfarrer@gmx.com" <ianfarrer@gmx.com>, Tomek Mrugalski <tomasz.mrugalski@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Benjamin Kaduk's Discuss on draft-ietf-dhc-mac-assign-07: (with DISCUSS and COMMENT)
Thread-Index: AQHWPU1CQLd28WDCJkeJIa7/mtj5+ajPOP+A//++doA=
Date: Mon, 08 Jun 2020 21:19:57 +0000
Message-ID: <B4521F2E-E996-4679-8F6E-D5A2E4E2C5E6@cisco.com>
References: <159159050144.17160.2937263097536871303@ietfa.amsl.com> <20200608211431.GZ58497@mit.edu>
In-Reply-To: <20200608211431.GZ58497@mit.edu>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/16.37.20051002
Content-Type: text/plain; charset="utf-8"
Content-ID: <8E689D7615F9664F86468211B7A5DC61@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4f6b59d9-93ec-4208-6851-08d80bf1b243
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jun 2020 21:19:57.6902 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rf/nwW6awv0Zeyxoj+7Vr3a6NB1RaZMGxuu2LZT5IFKMei5FsiZ8JHaAeLUQMfeP
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR11MB2674
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/9TwhrByqRirrKdIfpsXC3GJOOBI>
Subject: Re: [dhcwg] Benjamin Kaduk's Discuss on draft-ietf-dhc-mac-assign-07: (with DISCUSS and 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, 08 Jun 2020 21:20:05 -0000

I haven't had a chance to go through your extensive review -- thanks!

But the text here is supposed to be:

        The Identity Association for Link-Layer Addresses option (IA_LL
        option) is used carry an IA_LL, the parameters
        associated with the IA_LL, and the address blocks associated with the
        IA_LL.

This was supposed to be modeled after RFC8415's text for the IA_NA, etc. That text is:

   The Identity Association for Non-temporary Addresses (IA_NA) option
   is used to carry an IA_NA, the parameters associated with the IA_NA,
   and the non-temporary addresses associated with the IA_NA.

I'm not sure when the "one or more" crept in. Thanks for finding it.

- Bernie

On 6/8/20, 5:14 PM, "Benjamin Kaduk" <kaduk@mit.edu> wrote:

    On Sun, Jun 07, 2020 at 09:28:21PM -0700, Benjamin Kaduk via Datatracker wrote:
    > ----------------------------------------------------------------------
    > DISCUSS:
    > ----------------------------------------------------------------------
    > 
    > I have a couple points that might require a bit of discussion, but I
    > expect to be pretty easy to resolve:
    > 
    > (1) Can we double-check this text in Section 10.1:
    > 
    >    The Identity Association for Link-Layer Addresses option (IA_LL
    >    option) is used to carry one or more IA_LL options, the parameters
    >    associated with the IA_LL, and the address blocks associated with the
    >    IA_LL.
    > 
    > I am pretty sure that the "is used to carry one or more IA_LL options"
    > should actually be talking about IA_LLADDR options.  But if I'm wrong,
    > and this is saying that IA_LL can carry IA_LL, we should have a lot more
    > discussion about this recursive structure and how to interpret it.

    We may also want to check the "one or more" part, as Figure 3 of
    draft-ietf-dhc-slap-quadrant seems to show a workflow where IA_LL carries
    just QUAD and zero LLADDR.

    -Ben

[dhcwg] Benjamin Kaduk's Discuss on draft-ietf-dh… Benjamin Kaduk via Datatracker
Re: [dhcwg] Benjamin Kaduk's Discuss on draft-iet… Benjamin Kaduk
Re: [dhcwg] Benjamin Kaduk's Discuss on draft-iet… Benjamin Kaduk
Re: [dhcwg] Benjamin Kaduk's Discuss on draft-iet… Bernie Volz (volz)
Re: [dhcwg] Benjamin Kaduk's Discuss on draft-iet… Benjamin Kaduk