|
Yup, this can be easily done. Will update this in the next
revision.
Cheers, Manav
We should
either remove this sentence or add a short section briefly explaining what
can be done to fix the gaps found.
I would vote for the latter.
Reading and having written one of the documents doing gap analysis, it is
my feeling that we gelling around a few ways to improve almost all the
protocols. The common requirement is for an ability to rollover the keys. You
already mention it so why not make it part of the solution. Better encryption
and HMAC is clearly another.
On Jan 25, 2012, at 3:07 PM, Bhatia, Manav (Manav) wrote:
Hi Mahesh,
Good Catch.
Initially the plan was to suggest mechanisms to fix the
gaps found, but then we left that out as we weren't sure if that
was in scope for a gaps analysis document. We should either remove this
sentence or add a short section briefly explaining what can be done to fix
the gaps found. We had left this section since the fixing part should be
done in the BFD WG and this is a KARP document.
Cheers, Manav
Manav,
Was there a plan to propose mechanisms to address the issues? I did
not see them in the draft.
The remainder of this document explains the details of how these
requirements fail to be met and proposes mechanisms for addressing
them.
On Jan 25, 2012, at 3:34 AM, Bhatia, Manav (Manav) wrote:
Hi, Many many moons ago Dacheng and I had written a short
draft doing BFD gap analysis as part of the KARP Phase 1. The draft was
briefly discussed in the BFD WG and this version incorporates the
comments we received there + some boiler plate changes. http://tools.ietf.org/id/draft-bhatia-zhang-karp-bfd-analysis-02.txtComments
on this version are welcome! Cheers,
Manav _______________________________________________ karp mailing
list karp at ietf.orghttps://www.ietf.org/mailman/listinfo/karp
|
