> 4) SDP is still causing some problems.
> ....
> Also, something that was recently pointed out to me: SDP is
> required to include at least one of a p= or e= line. On page
> 11 of RFC2327, it says:
>
> "Either an email field or a phone field must be specified.
> Additional email and phone fields are allowed."
>
This is at odds however with the list starting on page 6 which indicates that
p and e are both optional fields. Also, in the spirit of being forgiving, I
hope that all SDP implementations will accept an SDP body without either a p= or
e= line. Furthermore, these fields should be taken with a grain of salt. I
don't see much purpose in rejecting an SDP body because the p= field contains a
malformed phone number or the e= field contains a malformed e-mail field. These are
informative but not really authoritative.
Sean Olson
--
Sean Olson <[EMAIL PROTECTED]>
Ericsson Inc.
> --
> Adam Roach, Ericsson Inc. | Ph: +1 972 583 7594 | 1010 E. Arapaho, MS L-04
> [EMAIL PROTECTED] | Fax: +1 972 669 0154 | Richardson, TX 75081 USA
>
