Re: [tsvwg] SCTP NAT support, draft-stewart-natsupp-tsvwg-00

"Brian F. G. Bidulock" <bidulock@openss7.org> Tue, 26 January 2010 14:55 UTC

Return-Path: <bidulock@openss7.org>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C9753A6935 for <tsvwg@core3.amsl.com>; Tue, 26 Jan 2010 06:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJQvM09LAlCk for <tsvwg@core3.amsl.com>; Tue, 26 Jan 2010 06:55:24 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by core3.amsl.com (Postfix) with ESMTP id 261333A68BB for <tsvwg@ietf.org>; Tue, 26 Jan 2010 06:55:24 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (IDENT:qrqumrMRKr1pxjDJIho2+AdZaC4/31nO@ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.13.8/8.13.8/Debian-3) with ESMTP id o0QEtKsM012493; Tue, 26 Jan 2010 07:55:20 -0700
Received: from wilbur.pigworks.openss7.net (IDENT:AiOohLIZTQCeja+jL61SKGxyz2jCdMGY@localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.13.8/8.13.8/Debian-3) with ESMTP id o0QEtKuR013764; Tue, 26 Jan 2010 07:55:20 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.13.8/8.13.8/Submit) id o0QEtJAl013763; Tue, 26 Jan 2010 07:55:19 -0700
Date: Tue, 26 Jan 2010 07:55:19 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <20100126145519.GA11231@openss7.org>
Mail-Followup-To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Randy Stewart <randall@lakerest.net>, tsvwg <tsvwg@ietf.org>, Michael Tuexen <tuexen@fh-muenster.de>, draft-stewart-natsupp-tsvwg@tools.ietf.org, Dan Wing <dwing@cisco.com>, "James M. Polk" <jmpolk@cisco.com>
References: <7B4DD94D79534300BD1A8C79BAB93402@china.huawei.com> <XFE-SJC-212sBt8sBju00002534@xfe-sjc-212.amer.cisco.com> <3A6D764F-4FDC-4873-B900-43B219558493@lakerest.net> <04ab01ca9df8$738c3860$c2f0200a@cisco.com> <A03B1092-9896-42DA-A226-08B29D1C4643@lakerest.net> <4B5EA57D.9020301@ericsson.com> <20100126105530.GA2801@openss7.org> <4B5ED37A.5060309@ericsson.com> <20100126132153.GA6204@openss7.org> <4B5EF322.4040701@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4B5EF322.4040701@ericsson.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: tsvwg <tsvwg@ietf.org>, Randy Stewart <randall@lakerest.net>, Michael Tuexen <tuexen@fh-muenster.de>, Dan Wing <dwing@cisco.com>, "James M. Polk" <jmpolk@cisco.com>, draft-stewart-natsupp-tsvwg@tools.ietf.org
Subject: Re: [tsvwg] SCTP NAT support, draft-stewart-natsupp-tsvwg-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 26 Jan 2010 14:55:25 -0000

Magnus,

Magnus Westerlund wrote:                     (Tue, 26 Jan 2010 14:50:26)
> > 
> > On a related note: is RFC 4960 or SCTP ever going from PS to DS?
> > 
> 
> A good question. There are I think primarily two questions. To what
> extent is the Normative references of a status of DS or FS? (A certain
> amount of exceptions can be handled)
> 
> Then there is the question of Implementation reports. All functionality
> in SCTP needs to have been implemented in at least two different
> code-bases and be tested against each other. This needs a written
> report, please see RFC 5657 https://datatracker.ietf.org/doc/rfc5657/
> for more info.

<rant>
Nowadays you use SCTP just about every time you make a phone
call.  SIGTRAN deployment (another set of PS RFCs) is poised to
overtake SS7 in deployment for heaven's sake.  Certainly the
requirements of RFC 2026 and RFC 5657 can be met by surveying
the widespread existing implementations and weeding out any
esoteric optional things (such as, perhaps, hostname in INIT).
Considering its widespread production deployment with SIGTRAN, I
find it amazing that it is not yet a full Internet Standard,
especially when compared to a lackadaisical work like SIP which
has long enjoyed full Internet Standard status.
</rant>

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/