IETF Logo Mail Archive

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

"BRUNGARD, DEBORAH A" <db3546@att.com> Wed, 28 September 2016 11:27 UTC

Return-Path: <db3546@att.com>
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 30D2F12B0BE; Wed, 28 Sep 2016 04:27:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
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 glV-jm3N15R1; Wed, 28 Sep 2016 04:27:17 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93F3312B0E3; Wed, 28 Sep 2016 04:27:17 -0700 (PDT)
Received: from pps.filterd (m0049295.ppops.net [127.0.0.1]) by m0049295.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id u8SBPDrY029559; Wed, 28 Sep 2016 07:27:14 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049295.ppops.net-00191d01. with ESMTP id 25r4p3cxx2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 28 Sep 2016 07:27:14 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u8SBRDSs008356; Wed, 28 Sep 2016 07:27:13 -0400
Received: from mlpi407.sfdc.sbc.com (mlpi407.sfdc.sbc.com [130.9.128.239]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u8SBR67N008288 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 28 Sep 2016 07:27:10 -0400
Received: from MISOUT7MSGHUBAE.ITServices.sbc.com (MISOUT7MSGHUBAE.itservices.sbc.com [130.9.129.149]) by mlpi407.sfdc.sbc.com (RSA Interceptor); Wed, 28 Sep 2016 11:26:50 GMT
Received: from MISOUT7MSGUSRDE.ITServices.sbc.com ([169.254.5.162]) by MISOUT7MSGHUBAE.ITServices.sbc.com ([130.9.129.149]) with mapi id 14.03.0301.000; Wed, 28 Sep 2016 07:26:49 -0400
From: "BRUNGARD, DEBORAH A" <db3546@att.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>
Thread-Topic: Alexey Melnikov's Discuss on draft-ietf-pals-rfc4447bis-05: (with DISCUSS)
Thread-Index: AQHSGJW+Di8l19dUC0CBAf4X3YV5BqCOw11w
Date: Wed, 28 Sep 2016 11:26:48 +0000
Message-ID: <F64C10EAA68C8044B33656FA214632C85DD9E5BF@MISOUT7MSGUSRDE.ITServices.sbc.com>
References: <147496345142.20752.894991698937654778.idtracker@ietfa.amsl.com>
In-Reply-To: <147496345142.20752.894991698937654778.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.133.46]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-09-28_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609020000 definitions=main-1609280203
Archived-At: <https://mailarchive.ietf.org/arch/msg/pals/O84qXKI1Plth-Gf2pCpmCeG3HOU>
Cc: "stewart.bryant@gmail.com" <stewart.bryant@gmail.com>, "draft-ietf-pals-rfc4447bis.all@ietf.org" <draft-ietf-pals-rfc4447bis.all@ietf.org>, "draft-ietf-pals-rfc4447bis@ietf.org" <draft-ietf-pals-rfc4447bis@ietf.org>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>, "pals@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 11:27:20 -0000

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?

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

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.
> 
> 
>

v2.23.0 | Report a Bug | By Email