edge of the
> potential destinations of a call.
Under certain cases, I don't necessarily see this belief as
erroneous. Problem is in how a globally authoritative
response interacts with other features in a protocol.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Luce
c3261 seems to
do since the 6xx responses mask repairable responses
when forking occurs. *That* is the root of the problem.
Whether or not it is worth fixing is another debate.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Ill
lly,
if it has more intelligence and even more locations to derive, it
will do so ;-) It is only trying to be helpful.
> And in case the proxy wants to do it upon receipt of a response
> "destination doesn't exist", why should a 6XX avoid it?
'Cause rfc3261 says so
hoice?
Depends on a particular implementation. Some may consider this
to well be a 408.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurb...@alcatel-lucent.com
Web:
mplementors/2011-April/026979.html
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurb...@alcatel-lucent.com
Web: http://ect.bell-labs.com/who/vkg/
-class). Unfortunately, I do not remember
what we had in mind (maybe someone else can). If 6xx is not serving
its purpose, then maybe it should be deprecated. But that is a
discussion for another list, not this one.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
teracts badly
when forking is involved and there are other repairable error
responses that can be sent upstream.
[1]
https://lists.cs.columbia.edu/pipermail/sip-implementors/2011-April/026966.html
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naper
On 04/23/2011 02:43 PM, IƱaki Baz Castillo wrote:
> 2011/4/22 Vijay K. Gurbani:
>> Unlike rfc2543 where a received 6xx was immediately forwarded, in
>> rfc3261 this is not the case. A received 6xx response is not
>> quarantined until all other branches have generated a fin
2543
behaviour caused the UAC to actually receive two final
responses for a request, I would presume that most
proxies today will handle 6xx processing as specified
by rfc3261. In that context, I think a 604 may be the
best response, no?
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel
d
by rfc3261. In that context, I think a 604 may be the
best response, no?
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurb...@alcatel-lucent.com
Web: http://ect
lid-domain.net" will reach the same conclusion
as every other SIP server before it.
In that case, regardless of (a) or (b), a 604 seems appropriate
since trying elsewhere is not going to substantially increase the
odds of finding that domain.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Labor
ion
3.1 of [3].
OpenSSL version 1.0.0c-fips supports these extensions.
[1] http://tools.ietf.org/html/rfc5923#section-9.3
[2] http://tools.ietf.org/html/rfc5922#section-7.8
[3] http://tools.ietf.org/html/rfc4366#section-3.1
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lu
6 addresses.
[1] Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261
http://www.rfc-editor.org/rfc/rfc5954.txt
[2] Session Initiation Protocol (SIP) Torture Test Messages for
Internet Protocol Version 6 (IPv6)
http://www.rfc-editor.org/rfc/rfc5118.txt
- vijay
--
Vijay K. Gurbani,
SIP entities from different vendors implements the format,
logs will be produced in a standardized manner allowing
you to create sequence diagrams and perform other analytics.
[1] http://datatracker.ietf.org/wg/sipclf/
Cheers,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent
, Columbia University, New York, USA.
- Dr. Anja Feldmann, Deutsche Telekom Laboratory/TU Berlin, Germany.
The advance programme is available at the following URL:
http://iptcomm.org/IPTComm-2010-Programme.pdf
Registration is now open.
Best regards,
Vijay K. Gurbani and Gonzalo Camarillo,
IPTComm
Dear Colleagues: IPTComm is one of the few conferences dedicated
solely to IP telecommunications. Please excuse the posting to
this list, but I believe that the conference will be of interest to
many of the list participants.
Call for Industrial demonstrations and talks -- Deadline May 16, 2010.
ppear to
be expired, but in fact it is waiting for a RFC number (it is
currently blocked on draft-ietf-behave-turn-ipv6 to reach
maturity.)
Start with the second draft for a dual-stack SIP solution.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533,
we need all kinds of good and evil test
> scenarious.
You may want to take a look at rfc5118
(http://tools.ietf.org/html/rfc5118) for a set of IPv6-related
torture tests in SIP.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illi
, Germany.
CONFERENCE CO-CHAIRS
Georg Carle (Technical University of Munich)
Helmut Reiser (Leibniz Supercomputing Center)
TPC CO-CHAIRS
=
Gonzalo Camarillo (Ericsson Research)
Vijay K. Gurbani (Bell Laboratories/Alcatel-Lucent)
DEMONSTRATION AND INDUSTRY TALKS CO
Supercomputing Center, Munich, Germany.
CONFERENCE CO-CHAIRS
Georg Carle (Technical University of Munich)
Helmut Reiser (Leibniz Supercomputing Center)
TPC CO-CHAIRS
=
Gonzalo Camarillo (Ericsson Research)
Vijay K. Gurbani (Bell Laboratories/Alcatel-Lucent)
DEMONSTRATION AND
(Ericsson Research)
Vijay K. Gurbani (Bell Laboratories/Alcatel-Lucent)
DEMONSTRATION AND INDUSTRY TALKS CO-CHAIRS
==
Carol Davids (Illinois Institute of Technology)
Saverio Niccolini (NEC Laboratories Europe)
PUBLICITY CHAIR
===
Gregory Bond (AT
)
TPC CO-CHAIRS
=
Gonzalo Camarillo (Ericsson Research)
Vijay K. Gurbani (Bell Laboratories/Alcatel-Lucent)
DEMONSTRATION AND INDUSTRY TALKS CO-CHAIRS
==
Carol Davids (Illinois Institute of Technology)
Saverio Niccolini (NEC Laboratories Europe
ce-19).
ICE is in the RFC editor's queue.
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: v...@{alcatel-lucent.com,bell-labs.com,acm.org}
Web: http://ect.b
vior somewhere described (best practice)?
See http://tools.ietf.org/html/draft-ietf-sipping-v6-transition-07.
The draft is in RFC editor's queue.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: v...@{a
, Munich, Germany.
CONFERENCE CO-CHAIRS
Georg Carle (Technical University of Munich)
Helmut Reiser (Leibniz Supercomputing Center)
TPC CO-CHAIRS
=
Gonzalo Camarillo (Ericsson Research)
Vijay K. Gurbani (Bell Laboratories/Alcatel-Lucent)
DEMONSTRATION AND INDUSTRY
)
TPC CO-CHAIRS
=
Gonzalo Camarillo (Ericsson Research)
Vijay K. Gurbani (Bell Laboratories/Alcatel-Lucent)
DEMONSTRATION AND INDUSTRY TALKS CO-CHAIRS
==
Carol Davids (Illinois Institute of Technology)
Saverio Niccolini (NEC Laboratories Europe
s:
http://www1.ietf.org/mail-archive/web/sip/current/msg17617.html
Ciao.
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: [EMAIL PROTECTED],bell-labs.com,acm.org}
WWW:
the sort you have pointed out? If so, we devise a test or
two for inclusion.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: [EMAIL PROTECTED],bell-labs.com,acm.org}
WWW: http://www.alcatel-lucent.com/
instance.) The hashes will be different
if the presentation aspects of the addresses was changed during each
iteration.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: [EMAIL PROTECTED],bell-labs.com,ac
29 matches
Mail list logo