Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt
Wojciech Dec <wdec.ietf@gmail.com> Tue, 04 March 2014 10:31 UTC
Return-Path: <wdec.ietf@gmail.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA6A71A04E8 for <softwires@ietfa.amsl.com>; Tue, 4 Mar 2014 02:31:19 -0800 (PST)
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, HTML_MESSAGE=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 87xWu-3LsVwQ for <softwires@ietfa.amsl.com>; Tue, 4 Mar 2014 02:31:15 -0800 (PST)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id B7B1F1A00C0 for <softwires@ietf.org>; Tue, 4 Mar 2014 02:31:15 -0800 (PST)
Received: by mail-pa0-f48.google.com with SMTP id hz1so413082pad.7 for <softwires@ietf.org>; Tue, 04 Mar 2014 02:31:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vQDVDYBagx4aWcU+Ag1do1foFF5eWAQSeMfElPoz/pM=; b=qR0aljCfTk4Q+XlJUfOrrAFV2Mu+2BZwp7khYDhUC1bJS2ZIRycGyiY8Qpd2jSjUVj GuxyIHbHf8Lc6PHQ2f5ybS1k9GXVT3y/d1HPItPQ8FJwYYyxIjXkl5reMQp7b3BFV18k dPnHAPxC6r+wYGZ/eX3cbZ8cOU4+6NMcHh8xuy/91rxiCZZTlC7Ub7zpTkbREgEujrcj oKOe0bio0lvb7kmYvYemXPED6zpqCqQHkrbsxA7E5PzTgfj8zqgWnQsbERPxWEo1Lulj VWiIjhq7+Y9ZDe2TvOt3Qg1VztXY897fXiTWTOTOIM8rSWB7f0XRoO+S8NdfboxJxVvW yyOA==
MIME-Version: 1.0
X-Received: by 10.67.5.233 with SMTP id cp9mr4932399pad.147.1393929072692; Tue, 04 Mar 2014 02:31:12 -0800 (PST)
Received: by 10.70.1.70 with HTTP; Tue, 4 Mar 2014 02:31:12 -0800 (PST)
In-Reply-To: <B1B5DA58-5F1A-4157-AADD-BED6F750F151@gmx.com>
References: <20140211075445.17615.61208.idtracker@ietfa.amsl.com> <FD878467-904B-4441-95B4-11D4461A612E@employees.org> <CF237FDE.AACEB%ian.farrer@telekom.de> <CAFFjW4jOBfvnqCV4UH8qt0HA5zZ-35f+q5ZepzjnwGX5_Oj9Gg@mail.gmail.com> <8A1B81989BCFAE44A22B2B86BF2B76318A2CDB8ED2@HE111643.EMEA1.CDS.T-INTERNAL.COM> <CAFFjW4iP2KqNJFtJPr5rp0tzRwM5TPjaqiSP5r13JqbX46ao7w@mail.gmail.com> <CD1D4FF6-9509-43B4-AFC4-4F1AF99D0C4D@gmx.com> <CAFFjW4ibkj_xpTuXrbYjxkdxD=+qNzapCGPHJwXsZ-k0ZvGg-g@mail.gmail.com> <CF335888.AE89D%ian.farrer@telekom.de> <CAFFjW4hv5WBiqyw9jM+ZoLMGR5k49pjKXG0epnhrsOGoBBKMYA@mail.gmail.com> <00EEEB51-BA0E-480B-9DAA-F9F3BE3DD16E@gmx.com> <CF3A3BBE.EC844%ssenthil@cisco.com> <B1B5DA58-5F1A-4157-AADD-BED6F750F151@gmx.com>
Date: Tue, 04 Mar 2014 11:31:12 +0100
Message-ID: <CAFFjW4gg_1fEd11z=qFbYyyDKtcqkdbY2vTPWfApoSvXqOJpuw@mail.gmail.com>
From: Wojciech Dec <wdec.ietf@gmail.com>
To: Ian Farrer <ianfarrer@gmx.com>
Content-Type: multipart/alternative; boundary="047d7b15b1e53852b704f3c56785"
Archived-At: http://mailarchive.ietf.org/arch/msg/softwires/GeGMR9WMr3ii3Tne8nUHjfyWEVU
Cc: Softwires-wg <softwires@ietf.org>
Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Mar 2014 10:31:19 -0000
Yes, for the ICMP handling part, this works for me. Cheers On 3 March 2014 20:40, Ian Farrer <ianfarrer@gmx.com> wrote: > Hi Senthil, > > Good point. So, that would give us: > > For TCP and UDP traffic the NAPT44 implemented in the lwB4 SHOULD conform > with the behaviour and best current practices documented in > [RFC4787], [RFC508], and [RFC5382]. If the lwB4 supports DCCP, then the > requirements in [RFC5597] SHOULD be implemented. > > The NAPT44 in the lwB4 MUST implement ICMP message handling behaviour > conforming to the best current practice documented in [RFC5508] > If the lwB4 receives an ICMP error (for errors detected inside the IPv6 > tunnel), the node should relay > the ICMP error message to the original source (the lwAFTR). > > This behaviour SHOULD be implemented conforming to the section 8 of > [RFC2473]. > > > Works for me. OK with you Woj? > > Cheers, > Ian > > > On 3 Mar 2014, at 19:16, Senthil Sivakumar (ssenthil) <ssenthil@cisco.com> > wrote: > > Hi Ian, > > The NAPT44 in the lwB4 MUST implement ICMP message handling behaviour > conforming to the best current practice documented in [RFC5508] > If the lwB4 receives an ICMP message without the ICMP identifier fieldfor errors detected inside the IPv6 tunnel, the node should relay > the ICMP error message to the original source (the lwAFTR). > > Does the highlighted part mean "If the lwB4 receives an ICMP error > message", if so can you replace it as suggested? > I am not really sure why icmp identifier field is mentioned in there. > Other than that I am ok with the text. > > Thanks > Senthil > > > From: Ian Farrer <ianfarrer@gmx.com> > Date: Monday, March 3, 2014 1:54 PM > To: Wojciech Dec <wdec.ietf@gmail.com>, Senthil Sivakumar < > ssenthil@cisco.com> > Cc: "ian.farrer@telekom.de" <ian.farrer@telekom.de>, Softwires-wg < > softwires@ietf.org> > Subject: Re: [Softwires] I-D Action: draft-ietf-softwire-lw4over6-06.txt > > Hi Woj / Senthil, > > Putting the other discussions to the side for a moment, can we tackle > the fragmentation text you proposed as this should be easily resolvable? > > > > Suggested text: > > The NAT44 in the lwB4 MUST implement the behavior for ICMP message conforming to the > best current practice documented in [RFC5508 <http://tools.ietf.org/html/rfc5508>]. > If a LwB4 receives an ICMP error message without the ICMP > identifier field for errors that is detected inside a IPv6 tunnel, the > node should relay the ICMP error message to the original source. > This behavior SHOULD be implemented conforming to the section 8 of > [RFC2473] <http://tools.ietf.org/html/rfc2473#section-8>. > FOr TCP and UDP traffic the NAT44 implemented in the LwB4 SHOULD conform with the behavior > and best current practice documented in [RFC4787 <http://tools.ietf.org/html/rfc4787>], [RFC5508 <http://tools.ietf.org/html/rfc5508>], and > [RFC5382 <http://tools.ietf.org/html/rfc5382>]. > > What about the following wording, tweaked after reading RFC6888 > (Common Reqs for CGNs), replacing Section 5.2: > --- > For TCP and UDP traffic the NAPT44 implemented in the lwB4 SHOULD > conform with the behaviour and best current practices documented in > [RFC4787], [RFC508], and [RFC5382]. If the lwB4 supports DCCP, then the > requirements in [RFC5597] SHOULD be implemented. > > The NAPT44 in the lwB4 MUST implement ICMP message handling behaviour > conforming to the best current practice documented in [RFC5508] > If the lwB4 receives an ICMP message without the ICMP identifier field for > errors detected inside the IPv6 tunnel, the node should relay > the ICMP error message to the original source (the lwAFTR). > > This behaviour SHOULD be implemented conforming to the section 8 of > [RFC2473]. > ---- > > @Senthil, as this is a change to the wording previously agreed, could > you let me know if you're OK with the proposed new text? > > Cheers, > Ian > > >
- [Softwires] I-D Action: draft-ietf-softwire-lw4ov… internet-drafts
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… ian.farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… ian.farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Qi Sun
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Tom Taylor
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Suresh Krishnan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… ian.farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Lee, Yiu
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Satoru Matsushima
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Satoru Matsushima
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Qi Sun
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Satoru Matsushima
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Simon Perreault
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Lee, Yiu
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Axel.Clauberg
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Senthil Sivakumar (ssenthil)
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Simon Perreault
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Simon Perreault
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ted Lemon
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Suresh Krishnan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Tom Taylor
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Simon Perreault
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Lee, Yiu
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Qi Sun
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Yuchi Chen
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Tina TSOU
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Tom Taylor
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Lee, Yiu
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Lee, Yiu
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Qi Sun
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Cong Liu
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Qiong
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Yuchi Chen
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ian Farrer
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Yuchi Chen
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Ole Troan
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Lee, Yiu
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Tom Taylor
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Qiong
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Wojciech Dec
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… Tom Taylor
- Re: [Softwires] I-D Action: draft-ietf-softwire-l… ian Farrer