Re: [tsvwg] I-D Action: draft-ietf-tsvwg-natsupp-16.txt

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 27 July 2020 18:48 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77A0A3A1CCD for <tsvwg@ietfa.amsl.com>; Mon, 27 Jul 2020 11:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 tiYII-7uDD_D for <tsvwg@ietfa.amsl.com>; Mon, 27 Jul 2020 11:48:35 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id B74BD3A1BE0 for <tsvwg@ietf.org>; Mon, 27 Jul 2020 11:48:30 -0700 (PDT)
Received: from [192.168.1.70] (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 10EF31B00108; Mon, 27 Jul 2020 19:48:22 +0100 (BST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Mime-Version: 1.0 (1.0)
Date: Mon, 27 Jul 2020 19:48:21 +0100
Message-Id: <89F3315F-FFEF-4243-A2D8-FB300C76F703@erg.abdn.ac.uk>
References: <31246_1595851462_5F1EC2C6_31246_20_1_787AE7BB302AE849A7480A190F8B93303150315C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Cc: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
In-Reply-To: <31246_1595851462_5F1EC2C6_31246_20_1_787AE7BB302AE849A7480A190F8B93303150315C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
To: mohamed.boucadair@orange.com
X-Mailer: iPad Mail (17E262)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/lh4NTy6e0H9tkehfMmPr0GWDc1Y>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-natsupp-16.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2020 18:48:40 -0000


Hi Med,,

> On 27 Jul 2020, at 13:05, mohamed.boucadair@orange.com wrote:
> 
> Hi Michael, 
> 
> Please see inline. 
> 
> Cheers,
> Med
> 
>> -----Message d'origine-----
>> De : Michael Tuexen [mailto:Michael.Tuexen@lurchi.franken.de]
>> Envoyé : dimanche 26 juillet 2020 12:03
>> À : BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>
>> Cc : tsvwg@ietf.org
>> Objet : Re: [tsvwg] I-D Action: draft-ietf-tsvwg-natsupp-16.txt
>> 
>>> In any case, I'm afraid you will need to add details such as: amount
>> of time/resources a NAT can wait for out of order fragments. You may
>> reuse some of the text from RFC 6146, including the default frag
>> timeout.
>>> 
>>> * Consider this change to align with REQ-13 of RFC4787:
>>> 
>>> OLD:
>>>  When an SCTP packet has to be fragmented by the NAT function and
>> the
>>>  IP header forbids fragmentation a corresponding ICMP packet SHOULD
>> be
>>>  sent.
>>> 
>>> NEW:
>>>  When an SCTP packet has to be fragmented by the NAT function and
>> the
>>>  IP header forbids fragmentation, the NAT MUST send back an ICMP
>> message
>>>  "Fragmentation needed and DF set" to the internal host.
>> Changed to
>> <t>When an SCTP packet has to be fragmented by the NAT function and
>> the IP header forbids fragmentation, the NAT MUST send back a
>> corresponding ICMP message to the internal host.
>> 
>> since it covers IPv4 and IPv6.
> 
> [Med] The wording is IPv4-specifc: "When an SCTP packet ** has to be fragmented **".
> 
> You may consider my initial wording for IPv4 + add a new sentence to cover the IPv6 case.  
> 
> 
What do you think the IPv6 text should say?

Gorry

> 
> _________________________________________________________________________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
>