On 02/17/2011 09:26 AM, Pandurangan R S wrote:
> On Thu, Feb 17, 2011 at 6:40 PM, Kevin P. Fleming
> wrote:
>> It isn't supposed to be; local resolvers should only append their own
>> domain when the name they are asked to resolve does not contain any '.';
>> if it does, they are supposed to leav
On Thu, Feb 17, 2011 at 6:40 PM, Kevin P. Fleming wrote:
> It isn't supposed to be; local resolvers should only append their own
> domain when the name they are asked to resolve does not contain any '.';
> if it does, they are supposed to leave it alone.
As per DNS mechanism this does NOT sound t
On 02/16/2011 03:57 PM, Paul Kyzivat wrote:
> 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?
It isn't supposed to be; local resolvers should only append their
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
> 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
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-
2011/2/11 Brett Tate :
> 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 FQND.
For sure ".invalid" is not a valid FQND.
--
Iñaki Baz Castillo
___
Sip
@lists.cs.columbia.edu [mailto:sip-
>> implementors-boun...@lists.cs.columbia.edu] On Behalf Of Paul Kyzivat
>> Sent: Thursday, February 10, 2011 5:26 PM
>> To: sip-implementors@lists.cs.columbia.edu
>> Subject: Re: [Sip-implementors] Query on Handling of null ipv6 address
>
> To: sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] Query on Handling of null ipv6 address
> in SDP c= line.
>
> Adding to what brett said...
>
> Why is it necessary to have a separate null address for IPv6?
> Null is null. Won't an IPv4 null addr
Adding to what brett said...
Why is it necessary to have a separate null address for IPv6?
Null is null. Won't an IPv4 null address do? Even if your node doesn't
support IPv4, I would think it could support a *null* IPv4.
Thanks,
Paul
On 2/7/2011 7:09 AM, Brett Tate wrote:
>> Wh
: 'bindukumari.r'; sip-implementors@lists.cs.columbia.edu
> Subject: RE: [Sip-implementors] Query on Handling of null ipv6 address
> in SDP c= line.
>
> > What must be done when NULL IPv6 address in received
> > in SDP c= line,
>
> No MUST behavior has been defined f
> 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/responsive
location. If the UAS responds prior to the connection attempt, the UAS wi
sip-
> > implementors-boun...@lists.cs.columbia.edu] On Behalf Of bindukumari.r
> > Sent: Wednesday, February 02, 2011 4:25 AM
> > To: sip-implementors@lists.cs.columbia.edu
> > Subject: [Sip-implementors] Query on Handling of null ipv6 address in
> > SDP
entors-boun...@lists.cs.columbia.edu [mailto:sip-
> implementors-boun...@lists.cs.columbia.edu] On Behalf Of bindukumari.r
> Sent: Wednesday, February 02, 2011 4:25 AM
> To: sip-implementors@lists.cs.columbia.edu
> Subject: [Sip-implementors] Query on Handling of null ipv6 address in
> SDP c= line
Hi All,
Please clarify how to handle NULL IPv6 address in SDP c= line.
According to the following snippet of RFC 3264
"RFC 2543 [10] specified that placing a user on hold was
accomplished
by setting the connection address to 0.0.0.0. Its usage for putting
a call
on hold is
17 matches
Mail list logo
