[siprec] How many deliverables?

"Elwell, John" <john.elwell@siemens-enterprise.com> Wed, 06 April 2011 07:22 UTC

From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "siprec@ietf.org" <siprec@ietf.org>
Date: Wed, 06 Apr 2011 09:23:49 +0200
Thread-Topic: How many deliverables?
Thread-Index: Acv0K5KknwluuJp1Sd2DqCWhHDXRYg==
Message-ID: <A444A0F8084434499206E78C106220CA0875DC0BE3@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [siprec] How many deliverables?
Precedence: list

At present we have milestones for the following:

- Requirements (draft-ietf-siprec-req, already submitted to IESG)
- Architecture (draft-ietf-siprec-architecture)
- Metadata model (draft-ietf-siprec-metadata, to be posted shortly)
- Protocol (draft-portman-siprec-protocol is the sole candidate at present)

We also have draft-ram-siprec-metadata-format, which we anticipate adopting in some form in the fairly near future. The question was asked in Prague whether to create another milestone for metadata-format. Other possibilities are to do some mergers. In considering what documents to deliver, one consideration is a newcomer trying to make sense of what has to be implemented, which may lean us towards fewer documents and fewer cross references.

Some of the possible options:
A) Add metadata format as a 5th milestone and create a 5th deliverable.

B) Add metadata format to the metadata model deliverable. This would reduce cross-referencing between the two documents.

C) Add metadata format to the protocol deliverable. This would keep the stuff that needs to be implemented in one place.

Opinions?

John

[siprec] How many deliverables? Elwell, John