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 20:46 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 D33AE12D0E9; Tue, 5 Jul 2016 13:46:46 -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 KEiCsivQ28PX; Tue, 5 Jul 2016 13:46:45 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (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 42B8212B03C; Tue, 5 Jul 2016 13:46:45 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id r2so245999889oih.2; Tue, 05 Jul 2016 13:46:45 -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=PE3eBZX/Q1LqTTNbk5dvLKmTNYSSG6/QMzpwUesd3lA=; b=CSd20JkXriN3wAda+YYdSekfmVUS3tDatMHFF77DwfyqVA1VsQ4Of3OeACgayrsdWv mggw4O058+eh+Zb9E5b2ZqwXrVDUi26mJWI1F11Z1gfHqI0TyhmfwMFXHYl08tiGJcOF HSX7MKhk7/wZXPt9nU/994+It1o6Bzx3jHwK+go4BzPAINYlEUfZlFuI8oWiNRgkzgXC 9QsDxjllStLkqmeELWhin2EYVAvxrSsNNOwaqueimZeBjiwJk75hfFkvxNx6K+4XPdnh g0SO05ktQ6s3uTDkpKJs/f9dm8QxRIG9RXO90cqjA/ngjoRIM0zcUzhUkHXdUkper0V4 ueyw==
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=PE3eBZX/Q1LqTTNbk5dvLKmTNYSSG6/QMzpwUesd3lA=; b=LjCP+boM98DkHNZZUzo9WnabhWiXAGPWeomR6NtS7Zc3r2f0EKOLxupZM+hJQVz+sA bsGNdJG1CDK3YwbN+pyAn5dxjRXqVceyfhBbRKOta8Owv/T4lo3FMHGg0jVVeZDity8G 4RTr0jQHoLDZfjAm09lhZhChvnQAS+TRGeap3nrVZgAKsBS2TTJlYzNxg/vGbytQRLDu uLAdeQzrGKNlDRp05W45h62XAV7pFknUJCJs6MTf7EOSUOI8h0aTzeUIEo1It1GC1ZaZ zvsZNK6ZdzGGJEalM9l/5RxkEgQm56KPoyLucrDooo4ghSPubzXE1JsSShm69PGLUDOU MsyQ==
X-Gm-Message-State: ALyK8tITrh+MA/vBK5nYHauMW4qGxLqwTCMZd3EXjln0Z2tb3JEnS4dPN1FVCpenkMXnNiz6qP38UNPrxRdGig==
X-Received: by 10.157.43.10 with SMTP id o10mr11076595otb.110.1467751604624; Tue, 05 Jul 2016 13:46:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.52.242 with HTTP; Tue, 5 Jul 2016 13:46:30 -0700 (PDT)
In-Reply-To: <043401d1d6fd$d6bebf30$843c3d90$@ndzh.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>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 05 Jul 2016 16:46:30 -0400
Message-ID: <CAF4+nEFjDfXYEy2JC8DO6RVF5hLhjwJ6vC8z0TRhWS7pqhn1xw@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/2H5Tc2ryoZCwDR2KTOcguym2scs>
Cc: draft-ietf-trill-channel-tunnel@ietf.org, "trill-chairs@ietf.org" <trill-chairs@ietf.org>, "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>, 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 20:46:47 -0000

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
>>
>
>