Re: [Hipsec] Alexey Melnikov's Discuss on draft-ietf-hip-rfc5205-bis-09: (with DISCUSS)

Julien Laganier <julien.ietf@gmail.com> Fri, 05 August 2016 00:47 UTC

Return-Path: <julien.ietf@gmail.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF2D12DB53; Thu, 4 Aug 2016 17:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 Aqu6r0Dnvfqu; Thu, 4 Aug 2016 17:47:20 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (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 B904412D853; Thu, 4 Aug 2016 17:47:17 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id 4so134868025oih.2; Thu, 04 Aug 2016 17:47:17 -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; bh=W/FZbqRipe5eIzhCmXESD4j285QdeXxaIncfoe+eQ7k=; b=kKF3VI3GUrHSmQ7UPKIiJqE6zkDr5MJ6rFZqm7f6FheLlgPPkpS+sgmOqOe9piPApo 4BSXKB6ZTUgmWgOcb6x1LAkzPSa1y/ZUx36AYSy0u9oMYjyM6vp03D2acW8z81VqyBTW /6smfEUPSV549asK3Vaiv1QoBi2WlcgdV4/VQ36+gqrzDZY8rnV0ydzIRtAVILo58+s1 n/DkORIcRYoY63r5Xo4VwZJIzGnZy6KDzvyEvLdlzQ0j0mYDz7FW0cR/FrovbKtjQRZO vxgWFCkBcNMdt0hdwwMQ9+IDljwl1XqjDsY4Ro47ayBwokuFsiBg+EDP38JAVcyyKaPR 5HOg==
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; bh=W/FZbqRipe5eIzhCmXESD4j285QdeXxaIncfoe+eQ7k=; b=RpQIB7qYOx5muBba7xNo+AIopF+rOkznRpczomLzwNyGQmHuNbmdEHa87XknuyfwrJ QXM2hSBizyh0kKF+34suW8qIgiiScYjqib3I+zpMDhl3IJPUmIKOVodq3F25M+6y4XGp dPWq8xXCpuveL/JNnycjpuQMpZbB07Z6XIdbJ5adv1/qo4iUiIelWBpH7iMUt2x33hMD 1QiW3UM1vDH8iu971/viGG20nCPKZgT1XheZVa4aJzVubOGJN8lLBzf3wBF7nGs1tsK9 d16QJ3NyKKm4sMGJwuEqORPDOjPnv+naFXKmjGFZFLLOtdfW+Ae5ZN+Vae8ApbjoXZuW siDA==
X-Gm-Message-State: AEkoouvOLJxO5pryX6RQZOFkwjPpRyvIK+ju7kL4lY4OCH9+b/4JVtDCMbBjqVvQcNQu1vzxMz2p2L3qCxsLVg==
X-Received: by 10.202.102.208 with SMTP id m77mr4147225oik.24.1470358037131; Thu, 04 Aug 2016 17:47:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.63.52 with HTTP; Thu, 4 Aug 2016 17:47:16 -0700 (PDT)
In-Reply-To: <CAE_dhjtVzvwBci+LWzwO6BZNH9v-beTxcRkzNewZSYevKQ-xdQ@mail.gmail.com>
References: <20160706142213.7773.71894.idtracker@ietfa.amsl.com> <CAE_dhjtVzvwBci+LWzwO6BZNH9v-beTxcRkzNewZSYevKQ-xdQ@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
Date: Thu, 4 Aug 2016 17:47:16 -0700
Message-ID: <CAE_dhjuB3gi2Vamxgs56GGTnJKwW8iMy9f+U8PcFKEtmLuLhKA@mail.gmail.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/d7TnQBjsYcye0O5RdytKS7e15NI>
Cc: HIP <hipsec@ietf.org>, draft-ietf-hip-rfc5205-bis@ietf.org, hip-chairs@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [Hipsec] Alexey Melnikov's Discuss on draft-ietf-hip-rfc5205-bis-09: (with DISCUSS)
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2016 00:47:23 -0000

FYI I've addresses your concern with the IANA considerations as
discussed in the last draft revision.

Best,

--julien

On Fri, Jul 8, 2016 at 7:23 AM, Julien Laganier <julien.ietf@gmail.com> wrote:
> Hi Alexey,
>
> The IANA Considerations used to be a copy of RFC 5205 but someone
> asked that it be cleaned up. I will copy it back in the next revision.
> I will also clarify that the base64 encoding from section 4 is to be
> used, similar to DNSSEC RRs.
>
> Thanks.
>
> --julien
>
> On Wed, Jul 6, 2016 at 7:22 AM, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
>> Alexey Melnikov has entered the following ballot position for
>> draft-ietf-hip-rfc5205-bis-09: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5205-bis/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> This is the same as Ben's DISCUSS point, but I think this is important
>> enough to fix:
>>
>>  Please replicate the appropriate info from the RFC 5205 IANA
>> considerations. The similar section in this draft does not seem to stand
>> alone. Readers should not need to refer back to the obsoleted RFC to
>> understand this version.
>>
>> RFC 4648 actually has 2 base64 encodings, so you should say which section
>> number you mean (section 4 or section 5). I suspect you meant section 5.
>>
>>
>>
>>