Document: draft-ietf-sigtran-m2pa-11
Reviewer: John Loughney
Date: April 27, 2004

The above draft is ready to be shipped.  I think that this
is past its 'sell by' date - many people are waiting for it.

I note a few nits, in passing:

1) Formatting needs fixing, no indenting, for example.	

2) Security section seems a bit off.  I don't know about
   the M2PA usage scenarios - if it is interoperator or
   intraoperator.  If it is solely within an operator,
   perhaps "Site Security Handbook" is enough.  However,
   in general, I guess some text talking more about threats
   & how the protocol is used would be more helpful.  My
   guess is that this kind of signaling is high-value,
   so that if it gets knocked-out, there will be problems.

3) The folloing  section could probably be removed, I am unsure how it relates
   to this protocol.

  6.2 Protecting Confidentiality

  Particularly for wireless users, the requirement for confidentiality
  MAY include the masking of IP addresses and ports. In this case
  application-level encryption is not sufficient. IPSec ESP SHOULD be
  used instead [RFC2401].  Regardless of which level performs the
  encryption, the IPSec ISAKMP service SHOULD be used for key
  management.

4) The (and TCP) should probably be removed, as there is no mention
   of TCP usage elsewhere. 

  7.1 SCTP Payload Protocol Identifier

  The SCTP (and TCP) Registered User Port Number Assignment for M2PA
  is 3565.

5)   [RFC2434] - "Guidelines for Writing an IANA Considerations Section 
     in RFCs,"  shouldn't be a Normative reference.


6) "SS7 MTP2" should be spelled out in the document title.

that's about it,