Re: [Sigtran] M3UA IG Last Call
"Brian F. G. Bidulock" <bidulock@openss7.org> Tue, 17 February 2004 18:18 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23799 for <sigtran-archive@odin.ietf.org>; Tue, 17 Feb 2004 13:18:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At9nG-0004Tn-S5 for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 13:18:02 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1HII2sk017155 for sigtran-archive@odin.ietf.org; Tue, 17 Feb 2004 13:18:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At9nG-0004SC-1Y; Tue, 17 Feb 2004 13:18:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1At9mV-0004I0-8o for sigtran@optimus.ietf.org; Tue, 17 Feb 2004 13:17:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23651 for <sigtran@ietf.org>; Tue, 17 Feb 2004 13:17:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1At9mT-0006TR-00 for sigtran@ietf.org; Tue, 17 Feb 2004 13:17:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1At9lT-0006Kd-00 for sigtran@ietf.org; Tue, 17 Feb 2004 13:16:12 -0500
Received: from gw.openss7.com ([142.179.199.224] ident=[80Lq8LXwt1SzVWGOGt+Ofp0Bi0UnbV3j]) by ietf-mx with esmtp (Exim 4.12) id 1At9kW-0006Ch-00 for sigtran@ietf.org; Tue, 17 Feb 2004 13:15:12 -0500
Received: from ns.pigworks.openss7.net (IDENT:TA5eRtUJvjtkeZGKvkQSnXB0KHxGsEph@ns1.evil.openss7.net [192.168.9.1]) by gw.openss7.com (8.11.6/8.11.6) with ESMTP id i1HIFBI27087; Tue, 17 Feb 2004 11:15:11 -0700
Received: (from brian@localhost) by ns.pigworks.openss7.net (8.11.6/8.11.6) id i1HIFBL30911; Tue, 17 Feb 2004 11:15:11 -0700
Date: Tue, 17 Feb 2004 11:15:11 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Ong, Lyndon" <LyOng@Ciena.com>
Cc: "'sigtran@ietf.org'" <sigtran@ietf.org>
Subject: Re: [Sigtran] M3UA IG Last Call
Message-ID: <20040217111511.E29979@openss7.org>
Reply-To: bidulock@openss7.org
Mail-Followup-To: "Ong, Lyndon" <LyOng@Ciena.com>, "'sigtran@ietf.org'" <sigtran@ietf.org>
References: <829F074A10F98943A218DC363D09C92A014769C2@w2ksjexg06.oni.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <829F074A10F98943A218DC363D09C92A014769C2@w2ksjexg06.oni.com>; from LyOng@Ciena.com on Tue, Feb 17, 2004 at 10:10:04AM -0800
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id i1HIFBI27087
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Sender: sigtran-admin@ietf.org
Errors-To: sigtran-admin@ietf.org
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Id: Signaling Transport <sigtran.ietf.org>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Lyndon, I don't have a problem with that, providing that we will also be allowed to review and provide LC comments on the rfc3332bis draft once it is compiled and before it is advanced. --brian Lyndon Ong wrote: (Tue, 17 Feb 2004 10:10:04) > Hi Brian, > > I was hoping that review of the IG first would bring out > any contentious points to resolve. Reviewing the full > integrated spec might be more difficult, esp. without a > capability for change bars. > > Cheers, > > Lyndon > > -----Original Message----- > From: Brian F. G. Bidulock [mailto:bidulock@openss7.org] > Sent: Tuesday, February 17, 2004 9:15 AM > To: Ong, Lyndon > Cc: 'sigtran@ietf.org' > Subject: Re: [Sigtran] M3UA IG Last Call > > > Lyndon, > > I agree with a replacement document as well, however, can we have > the draft placed in that form for review? That is, should we not > then be having a WGLC on draft-ietf-sigtran-rfc3332bis-00.txt? > > Can we have one? > > Isn't a WGLC on draft-ietf-sigtran-m3ua-implementors-guide-07.txt > then premature? > > --brian > > Lyndon Ong wrote: (Mon, 16 Feb 2004 12:55:30) > > Hi Folks, > > > > It sounds like we may be ready to do a Last Call on the > > M3UA IG. If there are no objections, lets start up > > Last Call starting today, Feb. 16th and ending on Monday, > > March 1st. Please add "M3UA IG Last Call Comment" in the > > subject line for any emails. > > > > If we have agreement on the basic changes in the IG, > > the follow up question will be whether to release the > > IG itself as a document or incorporate the changes into > > a new M3UA spec. > > > > Thanks, > > > > L. Ong > > > > -----Original Message----- > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > > Sent: Monday, February 16, 2004 12:41 PM > > Cc: sigtran@ietf.org > > Subject: [Sigtran] I-D > > ACTION:draft-ietf-sigtran-m3ua-implementors-guide-07.txt > > > > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > This draft is a work item of the Signaling Transport Working Group of the IETF. > > > > Title : M3UA ImplementorÆs Guide > > Author(s) : J. Pastor, K. Morneault > > Filename : draft-ietf-sigtran-m3ua-implementors-guide-07.txt > > Pages : 70 > > Date : 2004-2-16 > > > > This document contains a compilation of all defects found up until > > the publication date for M3UA [RFC3332]. These defects may be of an > > editorial or technical nature. This document may be thought of as a > > companion document to be used in the implementation of M3UA to > > clarify errors in the original M3UA document. This document updates > > RFC3332 and text within this document supersedes the text found in > > RFC3332. > > > > A URL for this Internet-Draft is: > > http://www.ietf.org/internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt > > > > To remove yourself from the IETF Announcement list, send a message to > > ietf-announce-request with the word unsubscribe in the body of the message. > > > > Internet-Drafts are also available by anonymous FTP. Login with the username > > "anonymous" and a password of your e-mail address. After logging in, > > type "cd internet-drafts" and then > > "get draft-ietf-sigtran-m3ua-implementors-guide-07.txt". > > > > A list of Internet-Drafts directories can be found in > > http://www.ietf.org/shadow.html > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > Send a message to: > > mailserv@ietf.org. > > In the body type: > > "FILE /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt". > > > > NOTE: The mail server at ietf.org can return the document in > > MIME-encoded form by using the "mpack" utility. To use this > > feature, insert the command "ENCODING mime" before the "FILE" > > command. To decode the response(s), you will need "munpack" or > > a MIME-compliant mail reader. Different MIME-compliant mail readers > > exhibit different behavior, especially when dealing with > > "multipart" MIME messages (i.e. documents which have been split > > up into multiple messages), so check your local documentation on > > how to manipulate these messages. > > > > > > Below is the data which will enable a MIME compliant mail reader > > implementation to automatically retrieve the ASCII version of the > > Internet-Draft. > > > > > To: > > Date: Mon, 16 Feb 2004 12:55:11 -0800 > > Subject: > > > > > > > > > Content-type: message/external-body; access-type="mail-server"; > > server="mailserv@ietf.org" Content-Type: text/plain Content-ID: > > <2004-2-16123321.I-D@ietf.org> ENCODING mime FILE > > /internet-drafts/draft-ietf-sigtran-m3ua-implementors-guide-07.txt > > > > > -- > Brian F. G. Bidulock > bidulock@openss7.org > http://www.openss7.org/ -- Brian F. G. Bidulock bidulock@openss7.org http://www.openss7.org/ _______________________________________________ Sigtran mailing list Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran
- RE: [Sigtran] M3UA IG Last Call Ong, Lyndon
- [Sigtran] M3UA IG Last Call Ong, Lyndon
- [Sigtran] M3UA IG Last Call Comment Michael Tuexen
- RE: [Sigtran] M3UA IG Last Call Barry Nagelberg
- Re: [Sigtran] M3UA IG Last Call Michael Tuexen
- RE: [Sigtran] M3UA IG Last Call J.Javier Pastor (ML/EEM)
- RE: [Sigtran] M3UA IG Last Call Nitin Vairagare
- Re: [Sigtran] M3UA IG Last Call Brian F. G. Bidulock
- Re: [Sigtran] M3UA IG Last Call Brian F. G. Bidulock
- RE: [Sigtran] M3UA IG Last Call Ong, Lyndon
- RE: [Sigtran] M3UA IG Last Call Ong, Lyndon
- RE: [Sigtran] M3UA IG Last Call Samuel Dur D. Jeyaseelan
- Re: [Sigtran] M3UA IG Last Call Ian Rytina
- RE: [Sigtran] M3UA IG Last Call J.Javier Pastor (ML/EEM)
- RE: [Sigtran] M3UA IG Last Call john.loughney