Forwarding and Control Element Separation (ForCES) Implementation Experience
RFC 6369

Note: This ballot was opened for revision 03 and is now closed.

(Adrian Farrel) Yes

(Jari Arkko) No Objection

Comment (2011-05-26 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
   2.  NAT issues.  ForCES can be deployed everywhere and can run over
       SCTP/IP.  In order for the FE and CE to work behind NATs you must
       ensure that the TML ports are forwarded and that the firewall
       allows SCTP through.

This seems to be mixing NAT and firewall issues. Clearly, support NATs
requires for those NATs to be capable of handling SCTP traffic to begin
with. In addition, firewalls may have to be configured to let the traffic
through.

I found Section 3.3 very hard to understand for someone who is not
closely familiar with the Forces technology.

I don't understand why we need sections that talk about very generic topics,
like 3.4.2 that describes how to decode a protocol message.

And maybe more generally, I'm not sure what I learned from this document
in terms of real forces implementation experience. Where are the difficult
areas? Is the spec broken in places? Are there interoperability problems?
Is further work needed in some issue?

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

Comment (2011-05-23 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
   Developers of ForCES FEs and CEs should take the security
   considerations of the Forwarding and Control Element Separation
   Framework [RFC3746] and the Forwarding and Control Element Separation
   Protocol [RFC5810] into account.

Why is this a should and not a must?

(Gonzalo Camarillo) No Objection

(Ralph Droms) No Objection

Comment (2011-05-26 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
In this text:

3.3.  Model

   The model inherently is very dynamic.

What "model"?  The Forces data model?

More generally, I agree with Jari's comment about the content of the document.  I learned a little about potential issues in implementing the struct component (but no details).  Are there any other major implementation issues aside from struct components and handling protocol messages?

(Stephen Farrell) No Objection

Comment (2011-05-23 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
s/difficulty lie/difficulty lies/

(Russ Housley) No Objection

Comment (2011-05-24 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
  The Gen-ART Review by Francis Dupont on 9-May-2011 suggested several
  editorial changes.  Please consider them.

(Pete Resnick) No Objection

(Peter Saint-Andre) No Objection

(Robert Sparks) No Objection

(Sean Turner) No Objection