1. Let us not say this is a hard problem, it sounds like NP hard problem
(which indeed it's not)
Just rephrasing it, Suggested Resolution: Add a Requirements section that
lays out the problems that any solution must address.


>"#211: We should talk more about why this is a hard problem."
>
>This topic came up several times in different ways: we should talk about
>gaps, we should say more clearly why this is hard, etc.

>Suggested Resolution: Add a Requirements section that lays out the hard
>(or not so hard) problems that any solution must address.

Thanks and Regards,
Yogendra Pal
Ericsson, India
+919686202644

On Wed, Mar 21, 2012 at 6:56 AM, Stephen Hanna <[email protected]> wrote:

> Second issue. Please comment on the suggested resolution.
>
> Thanks,
>
> Steve
>
> -----Original Message-----
> From: ipsecme issue tracker [mailto:[email protected]]
> Sent: Tuesday, March 20, 2012 6:49 PM
> To: [email protected];
> [email protected]
> Subject: [ipsecme] #211: We should talk more about why this is a hard
> problem.
>
> #211: We should talk more about why this is a hard problem.
>
>  This topic came up several times in different ways: we should talk about
>  gaps, we should say more clearly why this is hard, etc.
>
>  Suggested Resolution: Add a Requirements section that lays out the hard
>  (or not so hard) problems that any solution must address.
>
> --
> -------------------------+-------------------------------------------------
>  Reporter:               |      Owner:  draft-ietf-ipsecme-p2p-vpn-
>  yaronf.ietf@…          |  problem@…
>     Type:  defect       |     Status:  new
>  Priority:  normal       |  Milestone:
> Component:  p2p-vpn-     |   Severity:  -
>  problem                |
>  Keywords:               |
> -------------------------+-------------------------------------------------
>
> Ticket URL: <http://trac.tools.ietf.org/wg/ipsecme/trac/ticket/211>
> ipsecme <http://tools.ietf.org/ipsecme/>
>
> _______________________________________________
> IPsec mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ipsec
>



--
_______________________________________________
IPsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipsec

Reply via email to