Re: [Hipsec] WGLC: HIP-based overlays

["Henderson, Thomas R" <[e-mail]>]

>
> > I would suggest:
> >
> > 1) merge draft-ietf-hip-bone, draft-ietf-hip-via, and
> > draft-ietf-hip-hiccups into one draft.
>
> The reason why these drafts are kept separate is that while
> the via and
> hiccups mechanisms are needed to build overlays, they are not specific
> to overlays and can be used in other contexts. Therefore, from a
> documentation perspective, it makes sense to have them in separate
> drafts. That much said, I agree that we need to make sure readers get
> the complete picture as soon as possible when they start reading the
> specifications. Let's work on reorganizing the sections and adding
> overview material so that the drafts explain up front what
> they are about.

I agree that the HIP DATA could be used in other contexts; I had another comment against that draft that if you decide to keep this as a separate draft, you could clarify some things in the beginning of the draft regarding the scope of the specification.

Regarding the via draft, it seems to me to be much more coupled with overlay forwarding, so I would suggest that either you describe the other non-overlay use case(s) for these parameters, or else merge it with HIP BONE.  Anyway, if you still feel that it is important to keep the via draft separate, I will not raise this point again.

Regards,
Tom