[tsvwg] Question about structure of “draft-ietf-tsvwg-natsupp-07.txt"

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Sun, 22 March 2015 13:19 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D42051A90C8 for <tsvwg@ietfa.amsl.com>; Sun, 22 Mar 2015 06:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.262
X-Spam-Level:
X-Spam-Status: No, score=-2.262 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, J_CHICKENPOX_16=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 x-PRpRrE2Xk5 for <tsvwg@ietfa.amsl.com>; Sun, 22 Mar 2015 06:19:09 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id ABA611A90C6 for <tsvwg@ietf.org>; Sun, 22 Mar 2015 06:19:09 -0700 (PDT)
Received: from [IPv6:2001:67c:370:136:d464:68a1:f110:b817] (unknown [IPv6:2001:67c:370:136:d464:68a1:f110:b817]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id A72251B0031F; Sun, 22 Mar 2015 13:19:27 +0000 (GMT)
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 21 Mar 2015 16:46:15 +0000
Message-Id: <AA20C43C-173B-4871-B222-DC37F83253BA@erg.abdn.ac.uk>
To: tsvwg@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsvwg/4kMYBl5zzzffovLEfP2v_E0kxLQ>
Cc: gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: [tsvwg] Question about structure of “draft-ietf-tsvwg-natsupp-07.txt"
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Mar 2015 13:19:12 -0000

Comments on “draft-ietf-tsvwg-natsupp-07.txt"

I have one major comment on the document as WG Chair, and some minor comments given in the next email (of course individual comments).

My major comment is that although I am really pleased this is readable and ties together the hosts and network interaction, I suggest it is a little hard as a NAT implementor to really understand what you need to put in your product. I’d be disappointed if this remains the case, since these are exactly the audience that needs to do something to increase deployability of SCTP. Some way needs to be found to point people to the correct areas that need them to take a`action.

One way this could be achieved, could be to make sure paragraphs trie to talk exclusively about host or NAT parts of the protocol. In some cases it would even be possible to make subsections to separate the text (but probably not always?).

If it were possible to do the above, then it would seem feasible and quite helpful to make a summary table pointing NAT implementors to the specific sections were there are things that need to be implemented to support SCTP. Such a list could also serve as a checklist for any implementor.

Best wishes,

Gorry