THIS RESEARCH GROUP IS NO LONGER ACTIVE
Host Identity Protocol Research Group (HIPRG)
HIPRG homepage & charter
IETF 82, Thurs. Nov 17, 0900-1130
The following are being worked on as IRTF stream documents.
| Draft name || Draft title || Status
Other documents for discussion at IETF 80:
Other documents published since IETF 79:
Documents for discussion at IETF 79 meeting:
Documents for discussion at IETF 78 meeting:
The following documents were discussed at IETF 77.
The following additional documents have been discussed in the past year.
Past Meeting Minutes and Materials
(migrate from old wiki)
(to be completed)
The purpose of advancing an independent submission to draft-irtf-hip status is to reflect that the HIP research group desires to work towards publishing the document as an IRTF-track RFC. It may also be the case that the document is later transferred to the HIP working group in the IETF if the HIP working group wants to adopt it.
The criteria for advancing an individual submission are:
- the draft represents the consensus of the HIP research group, or even if the draft is not a consensus position, the HIP research group reached consensus that it should be published as a product of the RG
- the document either already conforms to the guidelines posted at http://trac.tools.ietf.org/group/irtf/trac/wiki/IRTF-RFCs, or there is a commitment from the authors to bring the draft into alignment
- technical reviewers (non-authors) are identified
All drafts presented or posted for discussion on the HIP RG mailing list will be tracked on the wiki. Anyone may propose (on the mailing list) a draft to be advanced to research group status, at which time the chairs will ask on the mailing list whether there is support. There must be some level of positive acknowledgment by non-authors to help review and improve the document to take this action. If the chairs believe that the criteria are met, the draft can be advanced to research group status. Authors may be asked to resolve comments or concerns and come back to the list with a revised draft at a later time.
Once the document reaches IRSG state, a document shepherd will be appointed (typically one of the RG chairs):
The document shepherd will work with the authors to advance the document to the state at which it is ready for IRSG review: http://trac.tools.ietf.org/group/irtf/trac/wiki/IRTF-RFCs#IRSGReview.
While the RG will not officially have a "document shepherd" during the RG preparation stage, the technical reviewers reviewing this draft for the RG can look to the criteria in the above process in guiding their comments.
Not all HIP RG drafts will advance to IRSG review; some may migrate to the HIP WG, while some may never reach readiness for either state. To keep things moving along, draft status will be reviewed at the beginning of each research group meeting. Open issues may be tracked on the wiki or in an issue tracker. If a draft languishes (no progress on open issues) after being identified as a research group draft, it may be taken off the list of research group drafts at a future date.
Open Source Implementations