Re: [trill] Mirja Kühlewind's No Objection on draft-ietf-trill-channel-tunnel-09: (with COMMENT)

Donald Eastlake <d3e3e3@gmail.com> Tue, 05 July 2016 23:38 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 354A112B032; Tue, 5 Jul 2016 16:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 IED1OBlQm5UI; Tue, 5 Jul 2016 16:38:00 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 F135812B02F; Tue, 5 Jul 2016 16:37:59 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id f189so250877869oig.3; Tue, 05 Jul 2016 16:37:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=R/409pmKq8yQHVU85g9CpCKqtyoxOQr6/oPaYf8Sdw8=; b=bTXlofn7iiIQldabOApW5zP6Vo10S3hIGTfX4cGspDyUs7MSzbSMKykzknj9WSjRvd ZJutXyeg9bmMUidd5AN0zzxg3vFwQBHTmfZknT6LOnlnY5+xFjM5BOEO2H80sIe1VcB9 noommWTeC/e5MUtiukYaEpDSDwEgbzdPNNA+VvrL8fbl/curkG9NzTozo5Fz847ThV3s 9btQIBgZTmiID6TjGgMqD2XXvXF6sV+wP5LRPoCzbQFs6mFrMIIMXirezV5lNliUlsXv 6587AXUbu7Inaga5sV4C1aghG1hWbErhPldLssO6+kaSIIH+JT1wMsJUYSNpCPXUSTJ1 7wtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=R/409pmKq8yQHVU85g9CpCKqtyoxOQr6/oPaYf8Sdw8=; b=OY3EB5TzSaSturpOHPOqIvfGvhXmAc/ez3DtfhtDpLWZyIgMveh0S7tq894Ijw0MCo hBXXux4WOjos7dlRItHB7ZIOWQcJDRTVeQxNu9/fusQsNiR3F6jAfLQeyX5DNG54CZ2W AgM1/UZhG0vTMEZTbaQOXwW9FdlY4Ys/3vYVOOL10Cg0b/L4iOnBiH0oJIyTziEeNsYE QtEGj6pFX/GYgCO4fAFQQ7hN2BR7rR8SYX5mnZMiw/IkrIjpG6QIdvgfIL3sNkuWqR/+ bh+BjO70zdcI+ridVUne5u3SXenSpK0R04UYUCwkFQr1nCgbGW+ZJUdmPJKZ2AQBpgFt CiQw==
X-Gm-Message-State: ALyK8tJLrJARa5Je1KJlOiXcYkv6JqEKuqavLMm5tN4MMesSEDTN/umpNAJ3I+L1VnZdajVYbLykMlOKzodEQA==
X-Received: by 10.157.36.70 with SMTP id p64mr1868913ota.172.1467761879208; Tue, 05 Jul 2016 16:37:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.52.242 with HTTP; Tue, 5 Jul 2016 16:37:44 -0700 (PDT)
In-Reply-To: <CAF4+nEFjDfXYEy2JC8DO6RVF5hLhjwJ6vC8z0TRhWS7pqhn1xw@mail.gmail.com>
References: <20160704133205.2547.49641.idtracker@ietfa.amsl.com> <CAF4+nEFOVXuiM=Dt5+HgqF6UaTSjM7KucpYnzdETnV8ft5C8zg@mail.gmail.com> <1C9B8107-7FA4-458B-AFAF-F8C86741D598@kuehlewind.net> <043401d1d6fd$d6bebf30$843c3d90$@ndzh.com> <CAF4+nEFjDfXYEy2JC8DO6RVF5hLhjwJ6vC8z0TRhWS7pqhn1xw@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 05 Jul 2016 19:37:44 -0400
Message-ID: <CAF4+nEF5LNGtO2Ez_38LXheiKwrjGRNFShekJ2kY9E8ELqZe4w@mail.gmail.com>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/lP3PpJL0rN5g6oBHmLweOQy306U>
Cc: draft-ietf-trill-channel-tunnel@ietf.org, "trill-chairs@ietf.org" <trill-chairs@ietf.org>, The IESG <iesg@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Mirja Kühlewind's No Objection on draft-ietf-trill-channel-tunnel-09: (with COMMENT)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2016 23:38:02 -0000

Version -10 has been uploaded with the registries added (and GENART
review comments resolved).

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Tue, Jul 5, 2016 at 4:46 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> OK, I'll add registries.
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
>
> On Tue, Jul 5, 2016 at 4:43 PM, Susan Hares <shares@ndzh.com> wrote:
>> Mirja:
>>
>> The assignments imply a standards action for additional assignments.   The WG review did not request further details, but if the IESG feels this is appropriate (and it may well be), it could be changes to IANA registries without changing the sense of the WG LC.
>>
>> As WG co-chair, I do not think we need to go back to the WG to discuss this and Donald can set-up the registries in the document.
>>
>> Sue
>>
>> -----Original Message-----
>> From: Mirja Kuehlewind (IETF) [mailto:ietf@kuehlewind.net]
>> Sent: Tuesday, July 5, 2016 4:11 PM
>> To: Donald Eastlake
>> Cc: draft-ietf-trill-channel-tunnel@ietf.org; trill-chairs@ietf.org; The IESG; shares@ndzh.com; trill@ietf.org
>> Subject: Re: Mirja Kühlewind's No Objection on draft-ietf-trill-channel-tunnel-09: (with COMMENT)
>>
>> Hi Donald,
>>
>> I guess it’s up to the wg to decide if a registry is needed or not. I was just wondering why it was decided to not have one and wanted to double-check that this is the right thing to do. I’m fine with that.
>>
>> I would however, recommend to add a sentence saying that a document that would want to use any additional value would also need to set up a registry. And further, while table 4.1 says "Available for assignment by IETF Review“, table 3.1 doesn’t; i would recommend to add this there as well.
>>
>> Mirja
>>
>>
>>
>>> Am 04.07.2016 um 20:14 schrieb Donald Eastlake <d3e3e3@gmail.com>:
>>>
>>> Hi Mirja,
>>>
>>> Thanks for your comment. See below.
>>>
>>> On Mon, Jul 4, 2016 at 9:32 AM, Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
>>>> Mirja Kühlewind has entered the following ballot position for
>>>> draft-ietf-trill-channel-tunnel-09: No Objection
>>>>
>>>> ...
>>>>
>>>> ---------------------------------------------------------------------
>>>> -
>>>> COMMENT:
>>>> ---------------------------------------------------------------------
>>>> -
>>>>
>>>> One question: Why are there no IANA registries for tables 3.1 and 4.1?
>>>
>>> I believe that the first time a code point is specified, it is a
>>> judgement call whether or not to create an IANA registry. If not, then
>>> obviously the first subsequent document that defines additional values
>>> needs to set up a registry. But if it doesn't appear that there are
>>> likely to be any additional values for some time, I don't think it is
>>> necessary to specify a registry and decide on an allocation policy
>>> right away. By the time the first additional value needs to be
>>> assigned the level of demand and the registration policy may be
>>> clearer.
>>>
>>> However, if the IESG would like, it would certainly be simple enough
>>> to have these be IANA registries. (If that were done now I would
>>> suggest an allocation policy of IETF Review due to the limited number
>>> of values available.)
>>>
>>> Thanks,
>>> Donald
>>> ===============================
>>> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>> 155 Beaver Street, Milford, MA 01757 USA d3e3e3@gmail.com
>>>
>>
>>