Re: compatibility of RFC 4666 to RFC 3332
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
Lyndon, There were additional code points added to a number of fields and the state machine was changed in an incompatible fashion, particularly with regard to 'n'. IMO the version number should have been incremented. --brian Lyndon Ong wrote: (Fri, 17 Nov 2006 12:17:31) > Hi Folks, > > There seems to be some confusion about this. My understanding > after checking with the editors is that RFC 4666, although it > obsoletes RFC 3332, is still backwards compatible. An implementation > of 4666 should be able to work with an implementation of 3332 > and vice versa, thus there was no reason for a version change. > > The SSN and CIC were removed from Routing Key registration due > to interoperability issues, but these were optional parameters > in RFC 3332. > > Cheers, > > L. Ong > > _______________________________________________ > Sigtran mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/sigtran -- Brian F. G. Bidulock [email protected] http://www.openss7.org/