RE: Re: DRN Label Issues - Issue #2

"Haresign Lincoln" <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <849535E338E99741B7F7413F73253EDB04E8BD44@us-nj-mail1.comverse.com>
Brian,

You can change that to MAY.

Lincoln 

-----Original Message-----
From: Brian F. G. Bidulock [mailto:[email protected]] 
Sent: Wednesday, October 11, 2006 4:51 PM
To: Haresign Lincoln
Cc: Barry Nagelberg; [email protected]
Subject: Re: [Sigtran] Re: DRN Label Issues - Issue #2

Lincoln,

No you can't say what an SG SHOULD do toward the SS7 network either.
Please point out any of those.

--brian


Haresign Lincoln wrote:                                           (Wed,
11 Oct 2006 16:46:53)
> Brian,
> 
> I didn't say MUST, I said SHOULD.  You can change that to MAY.
> 
> Regards,
> Lincoln
> 
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:[email protected]]
> Sent: Wednesday, October 11, 2006 4:44 PM
> To: Haresign Lincoln
> Cc: Barry Nagelberg; [email protected]
> Subject: Re: [Sigtran] Re: DRN Label Issues - Issue #2
> 
> Lincoln,
> 
> Haresign Lincoln wrote:
(Wed,
> 11 Oct 2006 16:36:06)
> > Brian,
> > 
> > OK, then we can put something in the IG.
> > 
> > With regards to "towards the SS7 network", there are plenty of 
> > places in the RFC that say what an SG should do towards the SS7
network.
> > Perhaps I'm not understanding your point.
> > 
> 
> There are no other places in the RFC that say what the implementation 
> must do towards the SS7 network.  I assure you, I removed them all in 
> last call.  There is mention of what the SG MAY do, but not what it 
> must except in the case of DRN/TID label (which didn't really go 
> through a last call).
> 
> If you see any place in the RFC that says what an SG must do toward 
> the
> SS7 network, please point it out, because it needs to go in the IG
too.
> 
> --brian
> 
> 
> --
> Brian F. G. Bidulock
> [email protected]
> http://www.openss7.org/

--
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.