RE: Re: SP Status double endpoint

[email protected]
Newsgroups gmane.ietf.sigtran
Message-ID <OF27B35D6F.5220BE7A-ON48257341.000400CD-48257341.0005E96C@zte.com.cn>
>Broken results can be expected from broken software regardless of the
>protocol.  Solution: fix the software.

--->(jacky chen) sorry,i do not agree with you ,i think protocol should be
perfect to deal with it
,because it will cause traffice failure ,not automatic restoration.it can
not be receptible to the people using the equipment.

>See draft-bidulock-sigtran-corid-05.txt for equivalent procedures.

------->(jacky chen) it is so complex,i think RFC4666 MAY use change and
changeback procedure like MTP3, maybe it will be easy,
just add news messages and procedure like MTP3 does.
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.