Opened 8 years ago

Closed 8 years ago

#68 closed defect (fixed)

Server selection feedback from Dave Thaler

Reported by: dthaler@… Owned by: draft-ietf-pcp-server-selection@…
Priority: major Milestone: milestone1
Component: server-selection Version: 1.0
Severity: In WG Last Call Keywords:
Cc:

Description

My comments are in the marked up copy at http://research.microsoft.com/~dthaler/draft-ietf-pcp-server-selection-02.pdf
Much of it is editorial-only. A summary of the top technical feedback is below.

1) Relationship to RFC 6724 is confusing. For a given server should be

I) Construct set of *Candidate* Source Addresses based on app input and constraints in the PCP base spec (e.g., for a PEER it should just contain the app session's source address).
II) Sort list of destination addresses per RFC 6724 section 6

2) Should provide more guidance about when to use one vs multiple servers.

I believe the best answer is that by default, the client needs to use all PCP
servers that configure firewalls (i.e. external IP == internal IP in mapping).
When NATs are involved, then it is implementation specific... if the app can
deal with multiple IPs then it can use multiple servers that return different
external IPs.

Change History (1)

comment:1 Changed 8 years ago by dthaler@…

  • Resolution set to fixed
  • Status changed from new to closed

Addressed in -03.

Note: See TracTickets for help on using tickets.