Document: draft-ietf-speermint-architecture-17
Reviewer: Avshalom Houri
Review Date: 2011-02-02
IESG last call date: 2011-02-03

Summary: The document is ready as an informational RFC

Major issues: None.

Minor issues: None.

Nits/editorial comments:

Line 357:
   o  An SBE can contain a SF function.
->    o  An SBE can contain an SF function.

Line 421:
   Function (LUF) to determine a target address, and then is resolves
->    Function (LUF) to determine a target address, and then it resolves

Line 466:
   resolving these URIs to URIs for specific protocols such a SIP or
->    resolving these URIs to URIs for specific protocols such as SIP or

Line 485:
   particular order and, importantly, not all of them may be used.
->    particular order and, importantly, not all of them have to be used.

Line 537:
   SIP proxy.  Optionally, a SF may perform additional functions such as
->    SIP proxy.  Optionally, an SF may perform additional functions such as

Line 540:
   encryption.  The SF of a SBE can also process SDP payloads for media
->    encryption.  The SF of an SBE can also process SDP payloads for media

Line 582:
   The section defines uses of TLS between two SSPs [RFC5246] [RFC5746]
->    The section defines the usage of TLS between two SSPs [RFC5246]
[RFC5746]