The Mobile Application Part SECurity (MAPSEC) Domain of Interpretation (DOI) for the Internet Security Association and Key Management Protocol (ISAKMP)
draft-arkko-map-doi-08

[Ballot comment]
In section 4:   

      The definition of MAPSEC transforms in the 3GPP Technical
      Specifications such as [7] MUST specify if the use of Key Length
      is necessary and what the legal values are.

is a bit odd.  Can the IETF put a MUST requirement on another SDO?
by name?  Would it be as useful to write it as follows?

    To achieve interoperability, transform definitions MUST specify if the
  use of Key Length is necessary and what the legal values are.

[Ballot comment]
2.3:    MAP runs over IP or over UDP/IP?

4.2:    Is the 0x01 right- or left-justified in the four octets?  It would be clearer if you gave a 4-octet value.

The security considerations section is inadequate -- are there special MAPSEC-related vulnerabilities to be cautious of?  If not, say so.

[Ballot comment]
Section 7, IANA Considerations, 2nd paragraph:

s/by the the standardization bodies/by the standardization bodies/

I'm not really sure that sections 7.1 - 7.5 belong in the IANA Considerations section as they describe parameters to be managed by entities other than IANA.  They might better be described in a section of their own.

[Ballot comment]
Section 7, IANA Considerations, 2nd paragraph:

s/by the the standardization bodies/by the standardization bodies/

I'm not really sure that sections 7.1 - 7.5 belong in the IANA Considerations section as they describe parameters to be managed ny entities other than IANA.  They might better be described in a section of their own.