Opened 8 years ago

Closed 8 years ago

#70 closed defect (fixed)

IETF 88 meeting feedback on draft-ietf-pcp-port-set-04

Reported by: dthaler@… Owned by: draft-ietf-pcp-port-set@…
Priority: major Milestone: milestone1
Component: port-set Version: 1.0
Severity: Active WG Document Keywords:
Cc:

Description

From the IETF 88 meeting notes (http://www.ietf.org/proceedings/88/minutes/minutes-88-pcp)

[...]

Dave Thaler suggested that if port-set capability is added (or
removed), the PCP server can reset its Epoch to zero, which causes PCP
client to re-try using PORT_SET. New text is needed in the document for those things.
[See also discussion in the Jabber log.]

I don't see this in draft -04.

[...]

Simon: Possible to get multiple responses to a single request.
Dan: Add to Security Considerations.
Dan: If I'm missing one response out of the set, have to re-send request.
Dave: Need to know nonce, so this can still be an on-path attack.

I don't see this in draft -04.

Change History (1)

comment:1 Changed 8 years ago by dthaler@…

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

Fixed in -05

Note: See TracTickets for help on using tickets.