Re: [Ieprep] Proposed Revised Charter

> suggest a rewrite of these two paragraphs
>  
> <<<<<<<<<<<<
> 2. Nested VPNs require special considerations for routing and QoS if
> nodes in the path that make these decisions generally have limited
> information.
 > >>>>>>>>>>>
> 2. VPNs in the manner of IPSec--point-to-point tunnels that encrypt payload
> and header information--require special consideration for routing and QoS
> because some nodes on the path that make forwarding and scheduling
> decisions will have limited information.  Nested VPNs (tunnels in tunnels)
> or concatenated VPNs (tunnels terminated at a gateway node) VPNs both need
> to be considered.

this sounds like too much of a restriction - is there a reason to
restrict the VPN issues to ones relating to encryption?

> <<<<<<<<<<<<
> 4. Considering robustness of non-real-time applications with
> preferential treatments, as voice will not be the only application used
> by IEPREP.
 > >>>>>>>>>
> 4. While voice was the driving application for IEPREP in the past, 
> preferential
> treatments will need to be applied to all applications
> essential to emergency communications. Preferential treatment must
> address robustness of both voice and non-real-time applications that share
> the same infrastructure.

works for me

> I think we should also include a November goal of submitting an I-D on
> DoD requirements for precedence. Is that the same as your Feb 06 item?

fine by me

Scott

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep