Re: [Sigtran] SUA implementor's guide
Cullen Jennings <fluffy@cisco.com> Wed, 04 October 2006 04:09 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUy4H-0006qr-TQ; Wed, 04 Oct 2006 00:09:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUy4G-0006qj-Qy for sigtran@ietf.org; Wed, 04 Oct 2006 00:09:12 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUy4F-0006uP-GI for sigtran@ietf.org; Wed, 04 Oct 2006 00:09:12 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-4.cisco.com with ESMTP; 03 Oct 2006 21:09:11 -0700
X-IronPort-AV: i="4.09,252,1157353200"; d="scan'208"; a="1856421487:sNHT53775292"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-5.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9449Afl005231; Tue, 3 Oct 2006 21:09:10 -0700
Received: from [192.168.1.3] (sjc-vpn6-709.cisco.com [10.21.122.197]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k9448xid027038; Tue, 3 Oct 2006 21:09:03 -0700 (PDT)
In-Reply-To: <0901D1988E815341A0103206A834DA070109913C@mdmxm02.ciena.com>
References: <0901D1988E815341A0103206A834DA070109913C@mdmxm02.ciena.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <26B3AAE6-34C0-40C4-995D-E3A99FA6E295@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Sigtran] SUA implementor's guide
Date: Tue, 03 Oct 2006 21:09:00 -0700
To: sigtran@ietf.org
X-Mailer: Apple Mail (2.752.2)
DKIM-Signature: a=rsa-sha1; q=dns; l=2407; t=1159934950; x=1160798950; c=relaxed/simple; s=sjdkim5002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:Cullen=20Jennings=20<fluffy@cisco.com> |Subject:Re=3A=20[Sigtran]=20SUA=20implementor's=20guide; X=v=3Dcisco.com=3B=20h=3D3zBgJsjeTuH5n63DZCXuuQV4SVQ=3D; b=FLJjztasppI0llHwx0FG5cP3iLfNlwfWCIKXRfnWchtOxKs+h5GYH6uJNfQUHiLytirLQ+Zs udGkPrSVmViatVV7UZuc9L617Zhol7YwoodL1zP9vQ5ICQ7PFMiGRcDj;
Authentication-Results: sj-dkim-5.cisco.com; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: Barry Nagelberg <barryn@adax.com>, Lyndon Ong <Lyong@Ciena.com>
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
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>
Errors-To: sigtran-bounces@ietf.org
Glad to hear this is still moving forward. I got some promises when we reading earlier documents that some things I was concerned about "would be in the implementors guide" so I do want to hold folks to finishing that sooner or later :-) More importantly, I think some of this stuff if sufficiently complicated that outside a somewhat small group of folks, an implementor guide will really help this work be successful. On Sep 29, 2006, at 8:46 AM, Ong, Lyndon wrote: > Hi Guys, > > I suspect that Loede and John have been too busy to keep this > updated. Is there still interest in this? > > Cheers, > > Lyndon > > -----Original Message----- > From: Barry Nagelberg [mailto:barryn@adax.com] > Sent: Friday, September 29, 2006 8:30 AM > To: sigtran@ietf.org > Subject: RE: [Sigtran] SUA implementor's guide > > Lincoln, > > It has apparently expired and been deleted. It was issued on March 6. > > <snip> > Signalling Transport Working group L. > Coene > Internet-Draft > Siemens > Expires: September 7, 2006 J. > Loughney > > Nokia > March 6, > 2006 > > > SUA Implementor's guide > <draft-ietf-sigtran-sua-implementor-guide-03.txt> > <snip> > > Barry Nagelberg > Adax, Inc. > > -----Original Message----- > From: Haresign Lincoln [mailto:Lincoln.Haresign@comverse.com] > Sent: Friday, September 29, 2006 11:16 AM > To: sigtran@ietf.org > Subject: [Sigtran] SUA implementor's guide > > > > Just out of curiosity, what happened to the SUA implementer's guide? > > Was there any intention to update the SUA RFC in a similar manner > as was > done to the M3UA RFC? > > Regards, > Lincoln > > > > _______________________________________________ > Sigtran mailing list > Sigtran@ietf.org > https://www1.ietf.org/mailman/listinfo/sigtran > > _______________________________________________ > Sigtran mailing list > Sigtran@ietf.org > https://www1.ietf.org/mailman/listinfo/sigtran > > _______________________________________________ > Sigtran mailing list > Sigtran@ietf.org > https://www1.ietf.org/mailman/listinfo/sigtran _______________________________________________ Sigtran mailing list Sigtran@ietf.org https://www1.ietf.org/mailman/listinfo/sigtran
- RE: [Sigtran] SUA implementor's guide Ong, Lyndon
- [Sigtran] SUA implementor's guide Haresign Lincoln
- RE: [Sigtran] SUA implementor's guide Barry Nagelberg
- RE: [Sigtran] SUA implementor's guide Haresign Lincoln
- RE: [Sigtran] SUA implementor's guide john.loughney
- RE: [Sigtran] SUA implementor's guide Haresign Lincoln
- RE: [Sigtran] SUA implementor's guide Coene, Lode
- RE: [Sigtran] SUA implementor's guide john.loughney
- Re: [Sigtran] SUA implementor's guide Brian F. G. Bidulock
- Re: [Sigtran] SUA implementor's guide Cullen Jennings
- Re: [Sigtran] SUA implementor's guide Brian F. G. Bidulock
- RE: [Sigtran] SUA implementor's guide Ong, Lyndon
- RE: [Sigtran] SUA implementor's guide Haresign Lincoln
- Re: [Sigtran] SUA implementor's guide Brian F. G. Bidulock
- RE: [Sigtran] SUA implementor's guide Haresign Lincoln
- Re: [Sigtran] SUA implementor's guide Brian F. G. Bidulock
- RE: [Sigtran] SUA implementor's guide john.loughney
- Re: [Sigtran] SUA implementor's guide Brian F. G. Bidulock
- RE: [Sigtran] SUA implementor's guide Haresign Lincoln
- RE: [Sigtran] SUA implementor's guide Haresign Lincoln
- Re: [Sigtran] SUA implementor's guide Brian F. G. Bidulock
- Re: [Sigtran] SUA implementor's guide Brian F. G. Bidulock
- RE: [Sigtran] SUA implementor's guide Haresign Lincoln
- RE: [Sigtran] SUA implementor's guide Barry Nagelberg
- RE: [Sigtran] SUA implementor's guide Haresign Lincoln
- Re: [Sigtran] SUA implementor's guide Brian F. G. Bidulock
- RE: [Sigtran] SUA implementor's guide Coene, Lode
- [Sigtran] RE: TID Label Issues - Issue #1 Haresign Lincoln
- Re: [Sigtran] SUA implementor's guide Brian F. G. Bidulock
- Re: [Sigtran] SUA implementor's guide Brian F. G. Bidulock
- RE: [Sigtran] SUA implementor's guide Haresign Lincoln
- RE: [Sigtran] SUA implementor's guide john.loughney
- RE: [Sigtran] SUA implementor's guide Haresign Lincoln
- Re: [Sigtran] SUA implementor's guide Brian F. G. Bidulock
- [Sigtran] TID Label Issues - Issue #1 Brian F. G. Bidulock
- [Sigtran] TID Label Issues - Issue #2 Brian F. G. Bidulock
- [Sigtran] TID Label Issues - Issue #3 Brian F. G. Bidulock
- [Sigtran] DRN Label Issues -- Issue #1 Brian F. G. Bidulock
- [Sigtran] DRN Label Issues - Issue #2 Brian F. G. Bidulock
- [Sigtran] TID and DRN Label Issues - Issue #1 Brian F. G. Bidulock
- [Sigtran] DRN and TID Label Issues - Issue #2 Brian F. G. Bidulock
- [Sigtran] DRN and TID Label Issues -- Issue #3 Brian F. G. Bidulock
- [Sigtran] DRN and TID Issues - Issue #4 Brian F. G. Bidulock
- [Sigtran] DRN and TID Label Issues - Issue #6 Brian F. G. Bidulock
- [Sigtran] RE: TID Label Issues - Issue #2 Haresign Lincoln
- [Sigtran] DRN and TID Label Issues - Issue #7 Brian F. G. Bidulock
- [Sigtran] RE: TID Label Issues - Issue #3 Haresign Lincoln
- [Sigtran] RE: DRN Label Issues -- Issue #1 Haresign Lincoln
- [Sigtran] RE: DRN Label Issues - Issue #2 Haresign Lincoln
- [Sigtran] RE: TID and DRN Label Issues - Issue #1 Haresign Lincoln
- [Sigtran] DRN and TID Label Issues - Issue #8 Brian F. G. Bidulock
- [Sigtran] Re: TID Label Issues - Issue #1 Brian F. G. Bidulock
- [Sigtran] Re: TID Label Issues - Issue #2 Brian F. G. Bidulock
- [Sigtran] Re: TID Label Issues - Issue #3 Brian F. G. Bidulock
- [Sigtran] Re: DRN Label Issues -- Issue #1 Brian F. G. Bidulock
- [Sigtran] Re: DRN Label Issues - Issue #2 Brian F. G. Bidulock
- [Sigtran] RE: TID Label Issues - Issue #2 Haresign Lincoln
- [Sigtran] Re: TID and DRN Label Issues - Issue #1 Brian F. G. Bidulock
- [Sigtran] Re: TID Label Issues - Issue #1 Brian F. G. Bidulock
- [Sigtran] Re: TID Label Issues - Issue #2 Brian F. G. Bidulock
- [Sigtran] RE: TID Label Issues - Issue #1 Haresign Lincoln
- Re: [Sigtran] DRN and TID Issues - Issue #4 Brian F. G. Bidulock
- [Sigtran] RE: TID Label Issues - Issue #1 Haresign Lincoln
- [Sigtran] Re: DRN and TID Label Issues - Issue #7 Brian F. G. Bidulock
- [Sigtran] RE: TID Label Issues - Issue #3 Haresign Lincoln
- Re: [Sigtran] DRN and TID Label Issues - Issue #8 Brian F. G. Bidulock
- [Sigtran] Re: DRN and TID Label Issues -- Issue #3 Brian F. G. Bidulock
- [Sigtran] DRN and TID Label Issues Brian F. G. Bidulock
- [Sigtran] RE: DRN and TID Label Issues - Issue #5 Haresign Lincoln
- [Sigtran] DRN and TID Label Issues - Issue #5 Brian F. G. Bidulock
- [Sigtran] Re: DRN and TID Label Issues - Issue #2 Brian F. G. Bidulock
- RE: [Sigtran] Re: DRN Label Issues - Issue #2 Haresign Lincoln
- [Sigtran] RE: TID Label Issues - Issue #2 Haresign Lincoln
- RE: [Sigtran] DRN and TID Label Issues - Issue #8 Haresign Lincoln
- [Sigtran] RE: DRN and TID Label Issues - Issue #7 Haresign Lincoln
- [Sigtran] RE: DRN and TID Label Issues - Issue #2 Haresign Lincoln
- [Sigtran] RE: DRN and TID Label Issues -- Issue #3 Haresign Lincoln
- RE: [Sigtran] DRN and TID Issues - Issue #4 Haresign Lincoln
- Re: [Sigtran] Re: DRN Label Issues - Issue #2 Brian F. G. Bidulock
- [Sigtran] RE: DRN and TID Label Issues Haresign Lincoln
- [Sigtran] Re: TID Label Issues - Issue #1 Brian F. G. Bidulock
- RE: [Sigtran] DRN and TID Label Issues - Issue #8 Haresign Lincoln
- [Sigtran] Re: TID Label Issues - Issue #2 Brian F. G. Bidulock
- RE: [Sigtran] Re: DRN Label Issues - Issue #2 Haresign Lincoln
- [Sigtran] Re: DRN and TID Label Issues Brian F. G. Bidulock
- [Sigtran] RE: DRN and TID Label Issues - Issue #2 Haresign Lincoln
- RE: [Sigtran] Re: TID Label Issues - Issue #2 Haresign Lincoln
- Re: [Sigtran] DRN and TID Label Issues - Issue #8 Brian F. G. Bidulock
- Re: [Sigtran] Re: DRN Label Issues - Issue #2 Brian F. G. Bidulock
- RE: [Sigtran] DRN and TID Label Issues - Issue #8 Haresign Lincoln
- RE: [Sigtran] Re: DRN and TID Label Issues Haresign Lincoln
- RE: [Sigtran] Re: DRN Label Issues - Issue #2 Haresign Lincoln
- [Sigtran] Re: DRN and TID Label Issues - Issue #2 Brian F. G. Bidulock
- Re: [Sigtran] Re: TID Label Issues - Issue #2 Brian F. G. Bidulock
- Re: [Sigtran] DRN and TID Label Issues - Issue #8 Brian F. G. Bidulock
- Re: [Sigtran] Re: DRN and TID Label Issues Brian F. G. Bidulock
- Re: [Sigtran] Re: DRN Label Issues - Issue #2 Brian F. G. Bidulock
- [Sigtran] RE: DRN and TID Label Issues -- Issue #3 Haresign Lincoln
- [Sigtran] RE: DRN and TID Label Issues - Issue #7 Haresign Lincoln
- [Sigtran] Re: DRN and TID Label Issues -- Issue #3 Brian F. G. Bidulock
- [Sigtran] RE: DRN and TID Label Issues - Issue #2 Haresign Lincoln
- [Sigtran] Re: DRN and TID Label Issues - Issue #7 Brian F. G. Bidulock
- [Sigtran] Re: DRN and TID Label Issues - Issue #2 Brian F. G. Bidulock
- RE: [Sigtran] Re: DRN and TID Label Issues Haresign Lincoln
- Re: [Sigtran] Re: DRN and TID Label Issues Brian F. G. Bidulock
- [Sigtran] RE: DRN and TID Label Issues -- Issue #3 Haresign Lincoln
- [Sigtran] RE: DRN and TID Label Issues - Issue #7 Haresign Lincoln
- [Sigtran] Re: DRN and TID Label Issues -- Issue #3 Brian F. G. Bidulock
- [Sigtran] Re: DRN and TID Label Issues - Issue #7 Brian F. G. Bidulock
- RE: [Sigtran] Re: DRN and TID Label Issues Haresign Lincoln
- [Sigtran] RE: DRN and TID Label Issues -- Issue #3 Haresign Lincoln
- [Sigtran] Wrong Message Length Field. Aditya
- [Sigtran] Re: Wrong Message Length Field. Brian F. G. Bidulock