Re: Request for WG adoption of for draft-bryant-rtgwg-param-sync

Gmail <stewart.bryant@gmail.com> Fri, 04 August 2017 21:48 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F7F12708C; Fri, 4 Aug 2017 14:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 DKyiz36P_cNo; Fri, 4 Aug 2017 14:48:47 -0700 (PDT)
Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (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 E1C1212711E; Fri, 4 Aug 2017 14:48:46 -0700 (PDT)
Received: by mail-wr0-x241.google.com with SMTP id y67so3760477wrb.3; Fri, 04 Aug 2017 14:48:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:in-reply-to:mime-version:content-transfer-encoding :message-id:cc:from:subject:date:to; bh=EuJs2EWIg+0u7JxLL0bJ3jZMgLD93gu0nSa8CIU8L88=; b=mYSf8TyrhWSH7ruauRWdPdFgExqdXFwUGgpUEHFCr16zeHuL5QwVcahZtvZ8SRp1lI x88hJ04pHBMZf3pbjnQT7wqL2K0qbfYzeWCyjZKsAKoBL1R12wClPlIYTuzjVQaVnX2d 9SHIV2arPUBciVVhFbmtTWxBKWxG5l1Jjjp5GuQdugAQuZHFc0MTDw2Evr8bbEwnV5yD 1VMeuM6thMdyr7w/nmEBHO9KkGFy57n0bweOwcopv4lO5RSrhS0UDmjixQBwrDmkKCtl NY99llk4Hcn0xf60jpzBKYWE/Q9kXiPgi6yRzx6GSR+Fx+1yaPikYL+qrnIyA3u0E1bS TEKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:in-reply-to:mime-version :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=EuJs2EWIg+0u7JxLL0bJ3jZMgLD93gu0nSa8CIU8L88=; b=VdaCxjVOa2FB05RSSHgI3slnm01znUwlqX2yFdKqmzQn5zOk/z/IKEFDRo4jX3iB4H ynIHBlabXbdpL6Ww74oJ8H4TBUaJdcsHzNWMY5TNC66bA9uiKDij3yGkGFXEYQ4OhE+i VsvPK4qFRz2LWjER7la19oC9KrkKl6zXnorqfTRq1x5ffY6Hhwg+pno+XDuE2V4zY8+A pwmQH+9I45S16tBsV7FxFIqSbvwOsNgF+sogw7p0pzj+ZCae1Rk0Vzx+yPXCVFT0lGue a5U7ZumFFtmJ6lWyRPyAbBY4INBIKd63b1DQO3okytrrUUVdSWr0mrUvzqWtIhlH5Wwv 1UJA==
X-Gm-Message-State: AIVw112YKGAjPVO6l3PGzoLysBw8tSvhTOS6zWJvNh3pTrGG0sQVzJd5 c+j/yKKqP+y4vw==
X-Received: by 10.223.169.51 with SMTP id u48mr2732536wrc.109.1501883325402; Fri, 04 Aug 2017 14:48:45 -0700 (PDT)
Received: from [192.168.3.102] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id e76sm4498158wmd.36.2017.08.04.14.48.44 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 04 Aug 2017 14:48:44 -0700 (PDT)
References: <54854841-A47A-46B8-9563-4C7901179AF2@gmail.com> <a83a429f4c9a478ea2dc32fd95ea3e90@XCH-ALN-001.cisco.com>
In-Reply-To: <a83a429f4c9a478ea2dc32fd95ea3e90@XCH-ALN-001.cisco.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"
Message-Id: <80BF560A-6D02-40FF-9E9D-918EDDB6F66A@gmail.com>
Cc: Jeff Tantsura <jefftant.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>, "draft-bryant-rtgwg-param-sync@ietf.org" <draft-bryant-rtgwg-param-sync@ietf.org>, rtgwg-chairs <rtgwg-chairs@tools.ietf.org>
X-Mailer: iPad Mail (13G36)
From: Gmail <stewart.bryant@gmail.com>
Subject: Re: Request for WG adoption of for draft-bryant-rtgwg-param-sync
Date: Fri, 04 Aug 2017 22:48:43 +0100
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/jta5v_dGbv0XVt_mGv-HBQ8Juw8>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Aug 2017 21:48:50 -0000

NP, we should also change the draft name, but suggest that is done when the adoption poll completes.

Stewart

Sent from my iPad

> On 4 Aug 2017, at 22:44, Les Ginsberg (ginsberg) <ginsberg@cisco.com> wrote:
> 
> I appreciate that the authors have modified the draft in response to some comments I made - and I believe the changes satisfy my concerns.
> 
> I support WG adoption with one significant caveat - the title of the document needs to be modified to accurately reflect the scope of the revised draft. This is now confined to defining how to advertise "routing timer parameters" - it is no longer a generalized "any flavor of routing parameter" - which is one of the points I made in my objections.
> 
> Please modify the name to accurately reflect the redefined scope.
> 
>   Les
> 
> 
>> -----Original Message-----
>> From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Jeff Tantsura
>> Sent: Friday, August 04, 2017 12:46 PM
>> To: RTGWG
>> Cc: draft-bryant-rtgwg-param-sync@ietf.org; 'rtgwg-chairs'
>> Subject: Request for WG adoption of for draft-bryant-rtgwg-param-sync
>> 
>> Dear RTGWG,
>> 
>> The authors have requested the RTGWG to adopt for draft-bryant-rtgwg-
>> param-sync as the working group document.
>> 
>> WG expressed support during the last RTGWG meeting and the authors have
>> addressed all the comments received.
>> Please indicate support or no-support by August 18, 2017.
>> 
>> If you are listed as a document author or contributor please respond to this
>> email stating of whether or not you are aware of any relevant IPR. The
>> response needs to be sent to the RTGWG mailing list. The document will not
>> advance to the next stage until a response has been received from each
>> author and each individual that has contributed to the document.
>> 
>> Cheers,
>> Jeff
>> 
>> 
>> 
>> _______________________________________________
>> rtgwg mailing list
>> rtgwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtgwg