Re: [Iasa20] Last Call: <draft-ietf-iasa2-consolidated-upd-07.txt> (Consolidated IASA 2.0 Updates of IETF Administrative Terminology) to Best Current Practice

"Livingood, Jason" <Jason_Livingood@comcast.com> Mon, 18 March 2019 15:56 UTC

From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: "iasa20@ietf.org" <iasa20@ietf.org>
Thread-Topic: Last Call: <draft-ietf-iasa2-consolidated-upd-07.txt> (Consolidated IASA 2.0 Updates of IETF Administrative Terminology) to Best Current Practice
Thread-Index: AQHU2FHLj+roFh8WAEaYB/Hju2glcKYLSE9kgAZMnYCAAADJAA==
Date: Mon, 18 Mar 2019 15:56:40 +0000
Message-ID: <8A426BD4-BD3E-44D1-88EB-E5C2895B84FE@cable.comcast.com>
References: <155233988598.23126.17393958685508352412.idtracker@ietfa.amsl.com> <6.2.5.6.2.20190314044333.0ba709b8@elandnews.com> <71EDFD13-E4FA-4208-8648-C1EB7A78E2D4@cable.comcast.com>
In-Reply-To: <71EDFD13-E4FA-4208-8648-C1EB7A78E2D4@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/10.17.0.190309
Content-Type: text/plain; charset="utf-8"
Content-ID: <FC259D8768D8A84D99233A7FCAA98969@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/BpnG7JP8dXVX8uEnBcc5LJC9jdE>
Subject: Re: [Iasa20] Last Call: <draft-ietf-iasa2-consolidated-upd-07.txt> (Consolidated IASA 2.0 Updates of IETF Administrative Terminology) to Best Current Practice
Precedence: list

FYI for members of this WG list as well

On 3/18/19, 11:53 AM, "Livingood, Jason" <Jason_Livingood@cable.comcast.com> wrote:

    On 3/14/19, 11:42 AM, "ietf on behalf of S Moonesamy" <ietf-bounces@ietf.org on behalf of sm+ietf@elandsys.com> wrote:
        
    >    Section 2 only changes Section 3.3 of RFC 2028.  Are the other parts 
        of that RFC still relevant?
      
    [JL] Yes, the rest of RFC 2028 remains relevant, and it is not in scope for the IASA2 WG to materially change RFC 2028. The only change intended is to Section 3.3, as noted in Section 2 of https://tools.ietf.org/html/draft-ietf-iasa2-consolidated-upd-07. 
    
    >    Is the Managing Director still an ex-officio participant of the IESG?
      
    [JL] Yes, because no material changes to the IESG were in scope for the WG. The exact title of the position is the only change here. The current list if IESG members (for others reading this thread) is at https://www.ietf.org/about/groups/iesg/members/. 
    
    >    Who will now be part of the IESG as defined in RFC 3710?  Is that RFC 
        a "consensus" document [1]?
    
    [JL] There is no material change here either. As noted in response to your first question, the only change intended is to Section 2, as noted in Section 2 of https://tools.ietf.org/html/draft-ietf-iasa2-consolidated-upd-07. 
    
    >    RFC 3929 is a 2004 experiment.  Is that experiment still in use after 
        all those years?
    
    [JL] This was discussed extensively on the IASA2 WG mailing list between 12-February and 11-March, and in consultation with the RFC Editor and chairs of the IAB and IESG. The conclusion was reached that RFC 3939 be moved to historic but the IAB will need to take that step. As a result, this is a request the IAB, noted in the final paragraph of Section 1 of https://tools.ietf.org/html/draft-ietf-iasa2-consolidated-upd-07. 
        
    >    RFC 4633 is a 2006 experiment.  Is it still in use?
      
    [JL] See above - same as RFC 3929.
    
      
        As an overall comment, the "in-place" terminology updates make it 
        confusing to understand all those RFCs.
    
    [JL] Thanks for all your questions! Hope these responses helped.

[Iasa20] Last Call: <draft-ietf-iasa2-consolidate… The IESG
Re: [Iasa20] Last Call: <draft-ietf-iasa2-consoli… Livingood, Jason