RFC1191(bis)? RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 04 February 2016 19:40 UTC
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1C0B1ACE3C for <ipv6@ietfa.amsl.com>; Thu, 4 Feb 2016 11:40:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ppdhocazBP2Y for <ipv6@ietfa.amsl.com>; Thu, 4 Feb 2016 11:40:29 -0800 (PST)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (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 3BB441ACED6 for <ipv6@ietf.org>; Thu, 4 Feb 2016 11:39:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u14JdxU1004772; Thu, 4 Feb 2016 11:39:59 -0800
Received: from XCH-BLV-506.nw.nos.boeing.com (xch-blv-506.nw.nos.boeing.com [130.247.25.196]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u14Jdno4004521 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 4 Feb 2016 11:39:49 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-506.nw.nos.boeing.com ([169.254.6.100]) with mapi id 14.03.0235.001; Thu, 4 Feb 2016 11:39:42 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: RFC1191(bis)? RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: RFC1191(bis)? RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AdFfg3+BLtBoX934QD+GvVlTF9JUNw==
Date: Thu, 04 Feb 2016 19:39:41 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395E134@XCH-BLV-105.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/qq5WMh0ThLqrTlD8fcLmfiIYYXY>
Cc: IPv6 List <ipv6@ietf.org>, "Fred Baker (fred)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:40:30 -0000
While we are at it, should we also work on RFC1191(bis)? Yes, I know that that is IPv4, but it is used in mechanisms such as IPv6-over-IPv4 tunnels. AFAICT, the exact same edits that are being applied to RFC1981(bis) would apply equally to RFC1191(bis). Thanks - Fred fred.l.templin@boeing.com
- RFC1191(bis)? RE: 6MAN: Adoption call on draft-hi… Templin, Fred L