It was FQDN in RFC2327. Then, it became just IP4-address or IP6-address
in draft-ietf-mmusic-sdp-new-02 and -03, but went back to FQDN in
draft-ietf-mmusic-sdp-new-04. 

I don't know which is preferred for use with SIP. But it would be nice
if somebody would make up their mind.

        Paul

Jonathan Rosenberg wrote:
> 
> Jerry Wong wrote:
> 
> > Hi Jonathan,
> >
> > Just to clarify, where in RFC2327 does it mention that FQDN is not
> > allowed
> > in the c-line?  Because looking at RFC2327 pp.12-13 (under "Connection
> > Data"):
> >      "If a unicast data stream is to pass through a network address
> >      translator, the use of a fully-qualified domain name rather than an
> >      unicast IP address is RECOMMENDED."
> >
> > Is there a special condition somewhere (or some other RFCs) that I
> > missed?
> 
> Seems that this has been updated in draft-ietf-mmusic-sdp-new, as the
> current version (-04) only mentions IP addresses now.
> 
> I'm not sure I agree with it, but it appears to be whats stated. I've
> cc'd mmusic for more comments on why it was done, as I can't recall.
> 
> -Jonathan R.
> 
> --
> Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
> Chief Scientist                         First Floor
> dynamicsoft                             East Hanover, NJ 07936
> [EMAIL PROTECTED]                 FAX: (973) 952-5050
> http://www.jdrosen.net                  PH:  (973) 952-5000
> http://www.dynamicsoft.com
> 
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to