Re: Diagnostic Info in M3UA
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
Ambika, Ambika Tripathy wrote: (Fri, 13 Apr 2007 17:18:09) > > Hi All, > > I have one doubt related to diagnostic information in M3UA Error > message. > > Please let me know is there any limit of offending data message length > in the diagnostic information field. > > FYI: > > For IUA rfc-3057 it is mentioned that "the Diagnostic information > could contain the first 40 bytes of the offending message". RFC 3057 is obsolete. See RFC 4233. It says that the Diagnostic information SHOULD contain the offending message. No mention of 40 bytes. It also says that the Diagnostic information must contian enough of the offending message to identify the invalid Interface Identifier. > No no such in case of M3UA rfc-3332 or rfc-4666. RFC 4666 _does_ say 40 bytes. See errors on the bottom of Page 65. So it looks like you have things backward. --brian > > -- > Br, > Ambika Prasad Tripathy > Nethawk Networks > Cell: +91-94375 47730 -- Brian F. G. Bidulock [email protected] http://www.openss7.org/