Re: [lisp] draft-ietf-lisp-rfc6830bis-14

Dino Farinacci <farinacci@gmail.com> Mon, 20 August 2018 19:30 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2727B129619; Mon, 20 Aug 2018 12:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.598
X-Spam-Level:
X-Spam-Status: No, score=-0.598 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, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01] autolearn=no 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 vTOhHxDvI35P; Mon, 20 Aug 2018 12:30:02 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (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 36CD3128CF3; Mon, 20 Aug 2018 12:30:02 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id y9-v6so7080575vky.3; Mon, 20 Aug 2018 12:30:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=uH7UDop1VvvU0xQ1C7jTmV6jFmUP3VYPR+JciIKOf70=; b=DsjxkKCwXPcCjTe1X/etpSeNyLaW30+PLbeL5eKohiaYDxwg+9Cz78bS8Ih20Az4B3 iQ09uUe4WPX2yualONz4FzsifvXt9JsmZSiPEp8p6v65sCqjFia4Sz4UjQSquWhgoA/Z 3XQdxO0aawPS++7Pyrsc4wtgivJHJWN0djmBQrz7f5lZlO6rj7eo1C/9sJOINghExUNY JOLlzLNxKJrWITN9u7u2D0633NUhNpmK1Q+6AEp+U7lTuWURtVPWZUVFBKAdFNBfwVIe 1MOZH7/EgdRj3GO51zUZPSazcYRVV6D8YROD52ULy1r5wfEi85RY0tJ+NKsnX78oqT7g V4tg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=uH7UDop1VvvU0xQ1C7jTmV6jFmUP3VYPR+JciIKOf70=; b=a5heZ3AocA0oP4fUhCBhw+UqAk8dx/bkwU77XVLdmJujiZl0EOK3PXTN2a1K8+qeje QKgUXIbd5yiGruFvBslRL6S5vlvpU/KBC75Idd/ZdFRfIOoZA4aQhe0W1B0+TZuWtsLy IiKBeB3YxA8LDJBEqjs1qrVg6mIXxgYQZbF/cTN6NjQtoryNSmGzaNtECwMC76DVLjKR UpEWErv2NQURtFGxLZFMPddQoWZYIup2a9urbkkeNT7gADtlIXzQw6OKAqaCc489G6T9 9+KywnIjVj/a7yQtOk7DFZkgN1jpCzF6mXd7rcNwcUhPGsFz+1Fe6gy4tz6ox7RgkNsm x79g==
X-Gm-Message-State: AOUpUlFdfBb1zeG3ORywpMveBapv0ZromR22h/G5RL70dJimlMWZLn+l /SYevJH7hs3XT3oBf8S3Oo3yGrmQ
X-Google-Smtp-Source: AA+uWPy8ryw9gIUASYA5CXLF/cRX4+MOdLQMwjy3Vzavy2PbO6mAs92Z+WRNnsnSG9nhfWvHQqvG2Q==
X-Received: by 2002:a1f:dd47:: with SMTP id u68-v6mr30486084vkg.137.1534793401265; Mon, 20 Aug 2018 12:30:01 -0700 (PDT)
Received: from [10.10.0.236] ([45.73.155.132]) by smtp.gmail.com with ESMTPSA id 13-v6sm5088107vkf.34.2018.08.20.12.30.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Aug 2018 12:30:00 -0700 (PDT)
From: Dino Farinacci <farinacci@gmail.com>
Message-Id: <9BE375D7-50E1-4FF1-B59C-93C203CFBDD0@gmail.com>
Content-Type: multipart/mixed; boundary="Apple-Mail=_89A825BA-DB37-4020-9AD1-0E28AD907930"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Mon, 20 Aug 2018 15:29:59 -0400
In-Reply-To: <EAC5E3BA-AFF7-4187-96C3-72B82CF5DAE0@gmail.com>
Cc: draft-ietf-lisp-rfc6830bis.all@ietf.org, "lisp@ietf.org list" <lisp@ietf.org>
To: "Scott O. Bradner" <sob@sobco.com>
References: <6515577E-31A8-45DC-90DA-59C43817EAB7@sobco.com> <D7DCB6AE-D9AA-48E9-8D5C-FA7E7169E155@gmail.com> <600E5518-F884-42DA-80F2-4CF650C6BA60@sobco.com> <F5DF64DA-7974-456A-AC57-A25D160F253A@gmail.com> <4BAEBA48-2435-4B26-9A45-493A259E6250@sobco.com> <75299534-B274-40F4-AACB-F72105B2E248@gmail.com> <FE16C3DB-4B94-4B15-A377-0137F2A3F044@sobco.com> <EAC5E3BA-AFF7-4187-96C3-72B82CF5DAE0@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/gpqpbBxFnUjXRvvBrBHIyHo5UlA>
Subject: Re: [lisp] draft-ietf-lisp-rfc6830bis-14
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2018 19:30:09 -0000

And here is the diff for the same type of changes for 6833bis.

Thanks,
Dino


> On Aug 20, 2018, at 2:42 PM, Dino Farinacci <farinacci@GMAIL.COM> wrote:
> 
> WG, here is a diff with changes to reflect Scott’s comment. I wanted the list of implementator to-be-aware changes to get working group quick review.
> 
> I’m about to add a “Changes since RFC 6833” section to RFC 6833bis as well.
> 
> Thanks,
> Dino
> 
> <rfcdiff-rfc6830bis.html>
> 
>> On Aug 20, 2018, at 9:03 AM, Scott O. Bradner <sob@sobco.com> wrote:
>> 
>> a specific section only dealing with the changes since the RFC is best
>> 
>> there is too much noise in the per iteration log (which as you already note should be removed)
>> 
>> Scott
>> 
>>> On Aug 20, 2018, at 8:57 AM, Dino Farinacci <farinacci@gmail.com> wrote:
>>> 
>>> Note we do have a Document Change Log in Appendix B detailing the changes put in each version starting with RFC6830. Would that suffice? Or you still think a specific section is required?
>>> 
>>> Dino
>>> 
>>> <PastedGraphic-9.png>
>>> 
>>>> On Aug 20, 2018, at 8:44 AM, Scott O. Bradner <sob@sobco.com> wrote:
>>>> 
>>>> it would be best to have a section called “changes since RFC 6830” so there is no ambiguity that the section covers the changes
>>>> 
>>>> it would be fine to have that section just say “See  “Implementation Considerations.”
>>>> 
>>>> Scott
>>>> 
>>>> 
>>>>> On Aug 20, 2018, at 8:26 AM, Dino Farinacci <farinacci@gmail.com> wrote:
>>>>> 
>>>>> 
>>>>>> Hi Dino
>>>>>>> On Aug 20, 2018, at 8:18 AM, Dino Farinacci <farinacci@gmail.com> wrote:
>>>>>>> 
>>>>>>> There were little changes that an implementor would need to know about for the data-plane. But there were for the control-plane (i.e. RFC6833bis). But in either case, we’ll add a section in each bis document.
>>>>>> 
>>>>>> thanks - even if the section says “nothing to worry about” it will be useful
>>>>> 
>>>>> I’ll title it “Implementation Considerations” and place it between 17 and 18?
>>>>> 
>>>>> 14. Multicast Considerations  . . . . . . . . . . . . . . . . . .  29
>>>>> 15. Router Performance Considerations . . . . . . . . . . . . . .  30
>>>>> 16. Security Considerations . . . . . . . . . . . . . . . . . . .  31
>>>>> 17. Network Management Considerations . . . . . . . . . . . . . .  32
>>>>> 18. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  32
>>>>> 
>>>>> 
>>>>>>> 
>>>>>>> Are you going to be reviewer for 6833bis as well?
>>>>>> 
>>>>>> not assigned that yet but I will take a look
>>>>> 
>>>>> I will try to get the sections done in the next day or so. I’m at the 3GPP meetings this week.
>>>>> 
>>>>> Dino
>>>>> 
>>>>>> 
>>>>>> Scott
>>>>>>> 
>>>>>>> Dino
>>>>>>> 
>>>>>>>> On Aug 20, 2018, at 6:14 AM, Scott O. Bradner <sob@sobco.com> wrote:
>>>>>>>> 
>>>>>>>> I was just assigned to do a ops-dir review of  draft-ietf-lisp-rfc6830bis-14
>>>>>>>> 
>>>>>>>> this is not the review - that will come soon
>>>>>>>> 
>>>>>>>> but since this is a “bis” document that is to replace an existing RFC it needs to have a 
>>>>>>>> “changes since RFC 6830” section so that implementors of the earlier RFC will be able to tell
>>>>>>>> what they need to change to bring their code up to date without having to compare the 
>>>>>>>> RFCs line by line (and likely miss something)
>>>>>>>> 
>>>>>>>> Scott
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
>