Re: [Pals] Alexey Melnikov's Discuss on draft-ietf-pals-rfc4447bis-05: (with DISCUSS)

Alexey Melnikov <aamelnikov@fastmail.fm> Wed, 28 September 2016 12:25 UTC

Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: pals@ietfa.amsl.com
Delivered-To: pals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7528512B10C; Wed, 28 Sep 2016 05:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=KG4j9g+H; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=M9X3KWXu
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 3KKwi4QxeW5z; Wed, 28 Sep 2016 05:25:27 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E19612B102; Wed, 28 Sep 2016 05:25:27 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0737F20944; Wed, 28 Sep 2016 08:25:27 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute4.internal (MEProxy); Wed, 28 Sep 2016 08:25:27 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=qRC9UCGL5afl7rLJAmQi0+VdXYk=; b=KG4j9g +HMU01BAym6jo8k/jboqOsROdoadZ7jzE9n01C8zbGJUd0vTeE+hCXW+xdbO+1AT sBGkS8Q+GDezksmvxbMkw53Hv4hd0aiZg4mluz0ASzK5hDArwgn6eptmeUhWssqd wwdH1o2vRn8RJLddQv1FUGysHuSDKD+lbvICw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=qRC9UCGL5afl7rL JAmQi0+VdXYk=; b=M9X3KWXupExEv79JYx0qoGaRKF/TbR9jxWS53+/KjD6Ujuw 6Ulbe1pmpmuNDPmc+NoxF1py28uyZWl5JF+OFMdVIWXVY4Cv9nj2h9cw4QD2uEhY MpxZ9nggoMmbOoSvuHeNAn397f+ZAoaaZypdEyQmtrjyRHHUfFsuTexnNzUU=
Received: by mailuser.nyi.internal (Postfix, from userid 99) id D964197146; Wed, 28 Sep 2016 08:25:26 -0400 (EDT)
Message-Id: <1475065526.1935361.739575169.4F32B0B7@webmail.messagingengine.com>
X-Sasl-Enc: E+tQcmhM5sE/nz9f+f3drRshalKbplZLlo1VMu1zFZyn 1475065526
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, The IESG <iesg@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-3ce3fca2
Date: Wed, 28 Sep 2016 13:25:26 +0100
In-Reply-To: <F64C10EAA68C8044B33656FA214632C85DD9E5BF@MISOUT7MSGUSRDE.ITServices.sbc.com>
References: <147496345142.20752.894991698937654778.idtracker@ietfa.amsl.com> <F64C10EAA68C8044B33656FA214632C85DD9E5BF@MISOUT7MSGUSRDE.ITServices.sbc.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/52uEOeseJIcsbkLyaZeEktYYags>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, draft-ietf-pals-rfc4447bis.all@ietf.org, draft-ietf-pals-rfc4447bis@ietf.org, pals-chairs@ietf.org, pals@ietf.org
Subject: Re: [Pals] Alexey Melnikov's Discuss on draft-ietf-pals-rfc4447bis-05: (with DISCUSS)
X-BeenThere: pals@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Pseudowire And LDP-enabled Services dicussion list." <pals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pals>, <mailto:pals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pals/>
List-Post: <mailto:pals@ietf.org>
List-Help: <mailto:pals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pals>, <mailto:pals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2016 12:25:29 -0000

Hi Deborah,

On Wed, Sep 28, 2016, at 12:26 PM, BRUNGARD, DEBORAH A wrote:
> Hi Alexey,
> 
> As you say, this is a simple edit. For ISs, there are no clear procedures
> and we thought this was less risk. IANA was also ok.
> 
> How about we do this as an RFC Editor Note?

RFC Editor note is fine.

> If you could clear your DISCUSS before vacation that would be great.

Ok.

> Thanks,
> Deborah
> 
> 
> > -----Original Message-----
> > From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm]
> > Sent: Tuesday, September 27, 2016 4:04 AM
> > To: The IESG <iesg@ietf.org>
> > Cc: draft-ietf-pals-rfc4447bis@ietf.org; draft-ietf-pals-rfc4447bis.all@ietf.org;
> > Stewart Bryant <stewart.bryant@gmail.com>; pals-chairs@ietf.org;
> > stewart.bryant@gmail.com; pals@ietf.org
> > Subject: Alexey Melnikov's Discuss on draft-ietf-pals-rfc4447bis-05: (with
> > DISCUSS)
> > 
> > Alexey Melnikov has entered the following ballot position for
> > draft-ietf-pals-rfc4447bis-05: 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-pals-rfc4447bis/
> > 
> > 
> > 
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> > 
> > I have a simple issue with the IANA Considerations section which should
> > be easy to address:
> > 
> > The IANA section seem to be suggesting that IANA should do full search of
> > its registries to update all references to RFC 4447 to point to
> > rfc4447bis. I don't think it is easy for IANA to do that.
> > 
> > This document is obsoleting RFC 4447, which means that there is no need
> > to ever read RFC 4447 in order to implement this document. For that
> > reason, you should copy and paste content of the original RFC 4447's IANA
> > Considerations into this document. After that, add a sentence saying that
> > the only change is updating references to point to this document.
> > 
> > 
> > 
>