[pcp] UPnP IGD interworking [was RE: PCP failure scenarios & PCP state synchronization procedure]

["Dan Wing" <[e-mail]>]

> -----Original Message-----
> From: [e-mail]
> [mailto:[e-mail]]
> Sent: Wednesday, January 19, 2011 11:02 PM
> To: Dan Wing; [e-mail]
> Cc: 'Reinaldo Penno'
> Subject: RE: [pcp] PCP failure scenarios & PCP state synchronization
> procedure
...
> If the interworking function has no stable storage, I don't see how
> it can function as a UPnP IGD device at all.
> 
> Med: Dan, as a reminder we have wrote this in
> http://tools.ietf.org/html/draft-bpw-pcp-upnp-igd-interworking-01;
> 
> "5.4. Port Mapping Tables
> 
>    IGD-PCP Interworking Function MUST store locally all the mappings
>    instantiated by internal UPnP Control Points in the PCP Server.
> Port
>    Forwarding mappings SHOULD be stored in a permanent storage.  If
> not,
>    upon reset or reboot, the IGD-PCP Interworking Function MUST
>    synchronise its states as specified in Section 5.10."
> 
> We converged to this text instead of mandating permanent storage which
> is not met by low-end CPEs.
> 
> Reinaldo raised at that time "This is an extremely difficult
> requirement. Today most (if not all) CPEs only store in permanent
> storage manual configured mappings."

Let's consider today's UPnP IGD devices -- which (of course) do
nothing with PCP.  Those devices, today, also do not store their
UPnP IGD-created mappings in non-volatile RAM.  Thus, when they
reboot, they forget about their UPnP IGD-created mappings.

I don't see that PCP needs to take the burden to improve 
UPnP IGD.

-d