Re: [BEHAVE] [v6ops] New features in Legacy IPv4 (was Re: protocols without need for ALG ?)
t.petch <ietfc@btconnect.com> Thu, 13 August 2015 16:47 UTC
Return-Path: <ietfc@btconnect.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 422C61A1ADC; Thu, 13 Aug 2015 09:47:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level:
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_HELO_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 28oa1CX49O-U; Thu, 13 Aug 2015 09:47:04 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0740.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::740]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 573E41A1B12; Thu, 13 Aug 2015 09:47:03 -0700 (PDT)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ietfc@btconnect.com;
Received: from pc6 (81.151.167.91) by AMSPR07MB052.eurprd07.prod.outlook.com (10.242.81.27) with Microsoft SMTP Server (TLS) id 15.1.225.19; Thu, 13 Aug 2015 16:46:46 +0000
Message-ID: <02ab01d0d5e7$c4e75140$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Howard, Lee" <lee.howard@twcable.com>, Mark Smith <markzzzsmith@gmail.com>, Ca By <cb.list6@gmail.com>
References: <D1EF60F2.643E2%wesley.george@twcable.com> <CAD6AjGSmwogXb+OgGoPqSsvRL==h7YL763+sjWUY8_aqKkmTuw@mail.gmail.com> <CAO42Z2yLVh4AgmKKLK2bRF0x_-+nWAe3f__W9mJCKCRd+-MadA@mail.gmail.com> <D1F0BFBE.BED96%Lee.Howard@twcable.com>
Date: Thu, 13 Aug 2015 17:47:26 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.151.167.91]
X-ClientProxiedBy: HE1PR05CA0045.eurprd05.prod.outlook.com (25.164.28.13) To AMSPR07MB052.eurprd07.prod.outlook.com (10.242.81.27)
X-Microsoft-Exchange-Diagnostics: 1; AMSPR07MB052; 2:SxXWBQeAMd/q0Tx+Aa0lfDeevkcqcAAN8q/mRLIzrRtjCvrgL3XEA8WsG4SpLj0XVWdBADp0pmJ5D10tKRm3y5oaaGmyFbkQ172En+Hhcl4iOcTOThxf2a4rFURNvVs/S0gBdhpMz0gzFrgmmLdghv9iNegN4wB/EjJQA/f28fM=; 3:jxi+eiONeJbqTOcXrm5uq1I953G5wSBrZfUncVuSZ/20bPHibkLFhDaZEhPvmQsb0c86DKgFh3mDPpolA83eIBRt4n6Gkv7AmDZOThaPKTyTEmAbnNNCvyyZIl/2hMYepsoPUz+SbwJGuqY1MkJwlg==; 25:YTF+5XtmXEUDNrXhK9mAslxXGtFSgjU0RHOUweW8+GW2C48qeaejIa/TEcWxbnJChw1/ssIiyvUPVgZW0gqD2SsP7rj5lfatf3htI9bgIVrxpWmjKfN7q3Z+gvBOBsmc65Ku3ThQLEeFRQ85roAn9nFvI7fNJ1GhDZrLW/O/LmyDtFWbvc+aTXm9kpjH/exk543S8BYg8S+2IOpurYvdExIc2pB9NsEcDY02Bgys2xpV076RJ+JEeTDG4T94BnS3sfJ+DyayIDrz8yG2ZdJlLw==; 4:ADxVy0AsCSNDV05uUVNFyTAbWgBMEN9IeP0/zkiAUStoPfPzPOlz0olqXaehTCE5GkDHxjUEpay27DzIjRf/bZci1J04rtcwoXkt5CZiIWwJlRXy4wYxTcoTidY8+ql0kXjWOmve9UgTNbz7BSWqclac77B/WBcL4GQOma2RqDLrSR1MXXbnckmeWpqRq5Ad0IucPFC9ZwEW5HHF2s/Gy5nv7nXawImMkJvA8IaVp9p77iFcVjQ9SXezDVRpXjKZY69vevFiQVcxlCzhIZ3a6Llqf0wYbbBdUVjWcR5rI/M=
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB052;
X-Microsoft-Antispam-PRVS: <AMSPR07MB052837886AF5F742F5C8598A07D0@AMSPR07MB052.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:AMSPR07MB052; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB052;
X-Forefront-PRVS: 0667289FF8
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(377454003)(199003)(189002)(13464003)(4001540100001)(50226001)(84392001)(81156007)(61296003)(5001960100002)(105586002)(64706001)(5001860100001)(97736004)(33646002)(86362001)(1556002)(106356001)(47776003)(19580395003)(50466002)(5001830100001)(189998001)(87976001)(23756003)(44736004)(44716002)(62966003)(66066001)(122386002)(15975445007)(93886004)(116806002)(101416001)(5001770100001)(1456003)(81686999)(5890100001)(19580405001)(14496001)(77096005)(42186005)(50986999)(77156002)(76176999)(68736005)(92566002)(46102003)(62236002)(40100003)(81816999)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:AMSPR07MB052; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en;
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: 1; AMSPR07MB052; 23:UtASZy3gjBrBK8ex5XqjIBbD3ebAl9mePC4/9eXbC6lo8tU5sRgzDPHMDOdQ6RAVVOxogc2qXAIDDsFAujT3/+P8oRwaFtG2SN6f69VXe0PFeOfDcsLIVgVc+0hIowzRfu4j5SPImCA4M/6vbnNGNe8zkegZXvJfIDGobEPDU4qTFhpOE0HJ6n/Ver4BsHBab0NrrwRfXPLv4h0xwfcClsF2yxx0HdIvmqBWO3fDRJc3cS0790HVw42/pGa2bhKB9bKf4YJuxBl5EBYi5aTgZBq8g89oT9nGZWWjYJBhgJNlstaWbxOMnIPJakxjB7Zv5ZMwKUcrY3Xpxr5ykcE9VBAK1Z2jbwekp4h60NApEBakIqQ/tK+kubkYcidHBkDmCfoh3xHGdk/0F0dWoPFwIGwI+6qL/ZTE41/wbhs6WPUt1F3Eq7ynkRCRjTEQQX75fUq2r2/cfVy4MKEWkAPDHFS+yhfcd/W351yCimtShaks/NbRqvbyTgV+XIMISMXQDDxC7fzikvJ04IEUmAVcGsLniOtkJ97iaIKTPsiP5xHNl2ZorkGprWSea3oXLO9ck8H+6y1HKGdhtXXCld0sKLIRqHG1+KDbIgDBKjNww+tEOvrYpmrt7zvxcptu8l+BJdPIcdIcIgK25Zg22o+3qNXCmUgArXiyd0edNI6g4R72/+ZAYKiOAnFlQP+/+yId/LvvCPRn0LPlTDAXecYxhMds5atwm2wjXUT6AdSv9nk3Tzg5M5Wl9YK1oDaBj3u9N2U8Y6VyU3x2YRrMbZZelq9GCtxTWSwopLWrzOxoFk3foSj5JMCiehjHjw8JhMCp77x93YJo/y3ZqO8WvASEkHAmOl1T3zfxGsb5/MghJWpfQfEw885y6rKnubOmvEOxmug+7dLCMkxlO+zgK4OTDuCgaype689Anf0oqtaRoChwPD3/uvYk3pqs09dExIM5pVrIjBgPzLk7hd9/CQ1J7OtCTWUxt/pgFmnP9Xo43TnFVhH41krkLCMgSlyxigZmhn4wOd+XdUsp64qYx0InnaqHj/2GJYg5Fu3uBTAy5oO1gaQlQwlERB6KM3IHF23VFxC3EbABYAuKVgfRt2ZukNlTVQ0gNrK8RcIRnSMolk76YFrF068UBiltooRfRU5WSoRiFBt41zgQZ6n7PQnM8DgylUQAXRpdGE0GIVNpOMzheEtpm0sZbr5PLmE8dieG97mjmb4L3cHm9M9SMHGQECSDfdq3hMWwDQ/4w0ZCuiARbMYCqa1JylcbQftWGw7vLQHtf2ZEo9ybQej76LjurebcvSUGEULVqH7TjFxzJ0U/uF1yE90Ss9+hL3vj4Elu6IUlnPUd68NZZli24milrVg7AE8tXWWbCUm0XgwVEwg=
X-Microsoft-Exchange-Diagnostics: 1; AMSPR07MB052; 5:IgmnFLw9eIi4j0IEGAGJfYBA4n1BRJqVz8Fo6Yhve96ZVJbtc9WQmgcbavM5v/0bFLZIEW+pDVpofai7lGFebHbukkxwLkHU4fWpZuYLp7hWs4/7sKoDWINd7wvPNOwsytRxKpqUeEZDtyo6MtwUSg==; 24:+4dkTZJR8N8gUowqIHmdSNZPKtWXov41HQYZ6WYZaGgj9ECD5rpq981qtUfJf7HTDfnr7OY2IG/EOSeQET0XpDhRHjbOdFjCG4nnPDqLpT4=; 20:C6ttviou4sdTmlQTICezck/5OePIqPxeAO+zvIvEDbNZd7ci6Xva0HR8FhdxxsyOJ+qdKgOzz2MwsMH6w5rrXg==
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 Aug 2015 16:46:46.3604 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB052
Archived-At: <http://mailarchive.ietf.org/arch/msg/behave/kFGX5oi2af9FKzWakB9p-82oEC8>
Cc: v6ops@ietf.org, behave@ietf.org
Subject: Re: [BEHAVE] [v6ops] New features in Legacy IPv4 (was Re: protocols without need for ALG ?)
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/behave/>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Aug 2015 16:47:07 -0000
----- Original Message ----- From: "Howard, Lee" <lee.howard@twcable.com> To: "Mark Smith" <markzzzsmith@gmail.com>; "Ca By" <cb.list6@gmail.com> Cc: <v6ops@ietf.org>; <behave@ietf.org> Sent: Wednesday, August 12, 2015 2:25 PM >>> >>> Is it time to resurrect this draft and push it forward? It doesn't >>> explicitly prohibit work of the type proposed in the above drafts, but >>>I'd >>> like to think that the current language strongly discourages it. >>> https://tools.ietf.org/html/draft-george-ipv6-support-03 >>> >>> Wes George >> >> Yes. We clearly see that folks need the message to be unambiguous >> >Deprecating IPv4 would do the trick. Doesn't mean you can't use it, >doesn't mean it can't continue to be fixed, just means that it has >become the legacy Internet protocol. I searched in vain for an IETF definition of ³Deprecated,² although I did find some examples. Howard I saw 'deprecated' used in an IANA registry 29aug2013 and raised the issue of a lack of definition on the main ietf list. Since then, 5226bis has been updated to say that the term is in use but should not be. The term has long had a well-defined meaning in SMI. Tom Petch I found a definition of ³Historic² (sort of) in rfc2026 and an old clarifying draft draft-yevstifeyev-genarea-historic-03. All of those words seem to suggest that the deprecated/historic/obsolete protocol could still be used, but to be careful with it. I¹d call it a SHOULD NOT, meaning don¹t unless you have a really good reason. I would be delighted if somebody has pointers to better definitions. This work would need to happen in 6man or intarea WG, I think. I therefore offer no opinion here. Lee This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. _______________________________________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
- [BEHAVE] New features in Legacy IPv4 (was Re: [v6… George, Wes
- Re: [BEHAVE] New features in Legacy IPv4 (was Re:… Ca By
- Re: [BEHAVE] [v6ops] New features in Legacy IPv4 … Mark Smith
- Re: [BEHAVE] [v6ops] New features in Legacy IPv4 … Howard, Lee
- Re: [BEHAVE] [v6ops] New features in Legacy IPv4 … Mark Smith
- Re: [BEHAVE] [v6ops] New features in Legacy IPv4 … George Michaelson
- Re: [BEHAVE] [v6ops] New features in Legacy IPv4 … t.petch
- Re: [BEHAVE] [v6ops] New features in Legacy IPv4 … David Farmer