Re: [auth48] Correction: Re: [C381] [AD] RE: AUTH48: RFC-to-be 9299 <draft-ietf-lisp-introduction-15> for your review

Sandy Ginoza <sginoza@amsl.com> Thu, 08 September 2022 00:25 UTC

Return-Path: <sginoza@amsl.com>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01E22C14CE24; Wed, 7 Sep 2022 17:25:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9HUslW8NaRYN; Wed, 7 Sep 2022 17:25:00 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34306C14CE33; Wed, 7 Sep 2022 17:25:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 12E484243EF8; Wed, 7 Sep 2022 17:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UlDL54fOgGC7; Wed, 7 Sep 2022 17:25:00 -0700 (PDT)
Received: from smtpclient.apple (2603-8000-9603-b513-19d8-e26a-bdba-a84e.res6.spectrum.com [IPv6:2603:8000:9603:b513:19d8:e26a:bdba:a84e]) by c8a.amsl.com (Postfix) with ESMTPSA id C5F0D424B440; Wed, 7 Sep 2022 17:24:59 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <CAMMESswqtwHEF+2q=sKHaxHHyQBRw7C4KvFG3kqkLmJz6E3o+w@mail.gmail.com>
Date: Wed, 07 Sep 2022 17:24:30 -0700
Cc: RFC Editor <rfc-editor@rfc-editor.org>, acabello@ac.upc.edu, lisp-chairs@ietf.org, ggx@gigix.net, auth48archive@rfc-editor.org, damien.saucez@inria.fr, lisp-ads@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <ECADF7A4-19D1-4939-9E6C-F77DD26805E4@amsl.com>
References: <20220907050157.B644B4C29E@rfcpa.amsl.com> <60295C8F-818F-4685-807E-3D8EE3390543@amsl.com> <CAMMESswqtwHEF+2q=sKHaxHHyQBRw7C4KvFG3kqkLmJz6E3o+w@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/OnRGiqDbEWsXljJgWKfQv9R7JV8>
Subject: Re: [auth48] Correction: Re: [C381] [AD] RE: AUTH48: RFC-to-be 9299 <draft-ietf-lisp-introduction-15> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Sep 2022 00:25:04 -0000

Hi Alvaro,

Thanks for your review and approval.  We could have been more clear that we were asking about the updates since version -13 - sorry about that. 

We’ve marked your approval on the AUTH48 page <http://www.rfc-editor.org/auth48/rfc9299>. 

Thanks,
Sandy 


> On Sep 7, 2022, at 7:30 AM, Alvaro Retana <aretana.ietf@gmail.com> wrote:
> 
> Sandy:
> 
> Hi!
> 
> I looked at the diffs: https://www.rfc-editor.org/authors/rfc9299-rfcdiff.html.  It looks (from the date) like the rfc9299.original file is based on version -13 of the draft, but -15 is the latest in the datatracker.  
> 
> Ahh, now that I look at your question I realize that you’re asking about the changes between -13 and -15.   Yes, all those changes are fine.  Thanks for checking. :-)
> 
> Alvaro. 
>  
> 
> On September 7, 2022 at 1:07:59 AM, Sandy Ginoza (sginoza@amsl.com) wrote:
> 
>> Correction to the cluster number in the subject line - this is part of C381.  
>> Apologies for any confusion!  
>> 
>> > On Sep 6, 2022, at 10:01 PM, rfc-editor@rfc-editor.org wrote: 
>> >  
>> > Authors, 
>> >  
>> > While reviewing this document during AUTH48, please resolve (as necessary)  
>> > the following questions, which are also in the XML file. 
>> >  
>> > 1) <!-- [rfced] *AD, please approve the following changes: 
>> >  
>> > - updated and new text in Section 3.2 
>> >  
>> > - updates to the first paragraph of Section 3.3.1 
>> >  
>> > - removal of "using the native Internet core" in Section 3.4.3.1 
>> >  
>> > - update from "Internet global routing system" to "routing system 
>> > beyond the local LISP domain" in Section 3.5 
>> >  
>> > - removal of "Typical values of TTL defined by LISP are 24 hours" in 
>> > Section 4.1 
>> >  
>> > - new text and change from "IBGP" to "IGP" in Section 4.2 
>> >  
>> > - new paragraph at the end of Section 6 
>> >  
>> > - updates to the "To improve resiliency ..." paragraph in Section 8 --> 
>> >  
>> >