Thank you, folks:
I try to design a secure SIP system.
Then I ask below:
An actual scenario:
Alice->Atlanta->Biloxi->Dallas->Dave
In that sequence,
if Dave has received a request from Alice to Bob who is in Biloxi,
can Dave understand this request is correct?
There is fear that a malicious us
DNS isn't my *thing*, but IIUC, couldn't "whatever.invalid" be resolved
to an FQDN of "whatever.invalid.example.com" if the node doing the
resolving has "example.com" as its domain?
To be sure, wouldn't it be necessary to specify "whatever.invalid." ???
Thanks,
Paul
On 2/16/201
You can use History-Info header to store your history.
INVITE sip:1B at example.com
History-Info: ;index=1,
;index=1.1,
;index=1.2
Valdemar
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implem
The basic answer is that Timer B only has relevance within "Calling" state. It
is started when entering "Calling" state and stopped when (or ignore after)
exiting "Calling" state.
The following quotes are from RFC 3261 section 17.1.1.2.
"For any transport, the client transaction MUST start tim
Hi all,
I have got a question regarding the start and stop of TimerB in the SIP ICT
State Machine, I am quite confused with that part. I am asking this because
I could not get the exact info from RFC. Can anyone clarify this in a simple
way.
Thanks and Regards,
Siga
___
From: sip-implementors-boun...@lists.cs.columbia.edu
[sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Couret Tabt
[courett...@gmail.com]
I mean "How does SIP ensure the reasonability of a request forwarding?".
For example:
Alice->Atlanta->B
> It is indeed number 4; I think the text in the draft is fairly clear on
> that point.
>
> Neither 2 or 3 would be 'within the .invalid DNS TLD', and number 1 is
> not "a domain name within the .invalid DNS TLD'.
Thanks for the response since I wanted to be sure that the example shown with
the
On 02/16/2011 05:36 AM, Brett Tate wrote:
>>> The draft also discusses using ".invalid"; however as
>>> I mentioned within the following link, I not sure if
>>> that it is really formatted as a valid FQDN.
>>
>> For sure ".invalid" is not a valid FQDN.
>
> Thanks for the response. The following is
On 02/15/2011 09:20 PM, Couret Tabt wrote:
> Thanks,Castillo,
>
> I mean "How does SIP ensure the reasonability of a request forwarding?".
>
> For example:
>
> Alice->Atlanta->Biloxi->Dallas->Dave
>
> In that sequence,
> how does SIP ensure the authenticity of Biloxi that is a forwarder?
>
> Moreov
Hi Brett,
On Mon, 2011-02-07 at 04:09 -0800, Brett Tate wrote:
> > What must be done when NULL IPv6 address in received
> > in SDP c= line,
>
> No MUST behavior has been defined for the situation; it is not a hold.
>
> The UAS received a request to communicate with a non reachable/responsiv
> > The draft also discusses using ".invalid"; however as
> > I mentioned within the following link, I not sure if
> > that it is really formatted as a valid FQDN.
>
> For sure ".invalid" is not a valid FQDN.
Thanks for the response. The following is the exact snippet from
draft-ietf-sipping-
11 matches
Mail list logo
