The Early Session Disposition Type for the Session Initiation Protocol (SIP)
draft-ietf-sipping-early-disposition-03

[Ballot discuss]
Example IPv4 addresses used do not follow:

  Addresses used in examples SHOULD preferrably use fully qualified
  domain names instead of literal IP addresses, and preferrably use
  example fqdn's such as foo.example.com instead of real-world fqdn's.
  See [RFC2606] for example domain names that can be used.
  There is also a range of IP addresses set aside for this purpose:
      For IPv4 these are 192.0.2.0/24 (see [RFC3330])

Document draft-ietf-sipping-early-disposition-01.txt uses
- IP addresses in the range 192.0.0.x
- domain names that do not adhere to those set apart in RCFC2606
Here is an example out of the draft-ietf-sipping-early-disposition-01.txt
  v=0
  o=Bob 2890844725 2890844725 IN IP4 host.example2.com
  s=
  c=IN IP4 192.0.0.2
  t=0 0
  m=audio 30000 RTP/AVP 0

[Ballot discuss]
This is a DISCUSS on document clarity. And it's mainly on the informational of the pair.
Quote from Spencer Dawkins, Gen-ART reviewer:

One meta-issue -
both discuss the "early media" problem, but don't say quite the same
things. The authors overlap - Gonzalo should pick one presentation and
include it in one draft. In general, you have to read both drafts to
figure out what the relationship is between them, so a summary of the
relationship would help a lot.

draft-ietf-sipping-early-media-01.txt really needs to have someone go
through it who's not Gonzalo or Henning - there are lots of unexpanded
acronyms and references to things that they know, that aren't common
knowledge in the IETF, with no pointers given. While reading it, I
kept thinking how much it needed at least a couple of pictures showing
the early media problem. The language is a lot rougher than in
draft-ietf-sipping-early-disposition-01.txt, too.

draft-ietf-sipping-early-disposition-01.txt is pretty close to ready.
I didn't see any major problems.

[Ballot discuss]
In early media, the iana considerations section has the following
text to be inserted into the "Content-Disposition" registry.

early-session  the body describes an early communications
                        session, for example, an RFC 2327 SDP body

The others registered by IANA for SIP are in the "MAIL Content Disposition
Values and Parameters" registry at http://www.iana.org/assignments/mail-cont-disp

I'd like us to discuss whether we need to split this registry/header, as we seem
to have gotten into a state where lots of these don't actually make sense for
mail.

[Ballot discuss]
There are unexpanded acronyms, such as UAS and UAC.

There are no Security Considerations sections.  Apart from the usual sorts of things one might want to analyze in SIP messages, the issue of tariff evasion by use of early media needs to be discussed.

[Ballot discuss]
There are unexpanded acronyms, such as UAS and UAC.

There are no Security Considerations sections.  Apart from the usual sorts of things one might want to analyze in SIP messages, the issue of tarrif evasion by use of early media needs to be discussed.

[Ballot discuss]
draft-ietf-sipping-early-disposition-01:

  A security considerations section needs to be added.

  draft-ietf-sipping-early-media-01:

  A security considerations section needs to be added.
 
  The Bibliography needs to be replaced with normative and informative
  references.