Subject: Re: TSVWG Status Sept 2011
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-604--77080278
From: Francois Le Faucheur <flefauch@cisco.com>
In-Reply-To: <4E671F4E.5000200@erg.abdn.ac.uk>
Date: Wed, 7 Sep 2011 10:44:12 +0200
Message-Id: <BF647AC9-2AA9-4BF3-A539-B9C7D89F664E@cisco.com>
References: <4E671F4E.5000200@erg.abdn.ac.uk>
To: "James Polk M." <jmpolk@cisco.com>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg WG <tsvwg@ietf.org>
Precedence: list

--Apple-Mail-604--77080278
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi James,

On 7 Sep 2011, at 09:37, Gorry Fairhurst wrote:
>=20
> draft-ietf-tsvwg-intserv-multiple-tspec
>      WG interest in this topic recorded at IETF-78.
>     Charter update would be needed to progress this work.
>     5 Reviews needed to determine energy/technical direction.
>     Version -05 (presented in Beijing, IETF-79)
>     Version -06 (presented in Prague, IETF-80)
>     RSVP directorate was consulted.
>        2 reviews from RSVP-DIR received (Bruce Davie, ?).
>        2 additional reviews promised (Ken Carlberg, Francois LeF).

You have been looking into a potential restructuring of the encoding =
based on Lou's suggestion. If you're going to do this, I'd rather do the =
review on the updated document. If not, I can review the current =
version. I'm not arguing you should, or should not do that change, but =
can you let us know if/when you see that happening, so I plan the review =
accordingly?

Thanks

Francois=

--Apple-Mail-604--77080278
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
James,<div><br><div><div>On 7 Sep 2011, at 09:37, Gorry Fairhurst =
wrote:</div><blockquote type=3D"cite"><div><font =
class=3D"Apple-style-span" =
color=3D"#000000"><br></font>draft-ietf-tsvwg-intserv-multiple-tspec<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;WG interest in this topic recorded at =
IETF-78.<br> &nbsp;&nbsp;&nbsp;&nbsp;Charter update would be needed to =
progress this work.<br> &nbsp;&nbsp;&nbsp;&nbsp;5 Reviews needed to =
determine energy/technical direction.<br> =
&nbsp;&nbsp;&nbsp;&nbsp;Version -05 (presented in Beijing, IETF-79)<br> =
&nbsp;&nbsp;&nbsp;&nbsp;Version -06 (presented in Prague, IETF-80)<br> =
&nbsp;&nbsp;&nbsp;&nbsp;RSVP directorate was consulted.<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2 reviews from RSVP-DIR =
received (Bruce Davie, ?).<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2 additional reviews promised =
(Ken Carlberg, Francois =
LeF).<br></div></blockquote><div><br></div><div>You have been looking =
into a potential restructuring of the encoding based on Lou's =
suggestion. If you're going to do this, I'd rather do the review on the =
updated document. If not, I can review the current version. I'm not =
arguing you should, or should not do that change, but can you let us =
know if/when you see that happening, so I plan the review =
accordingly?</div><div><br></div><div>Thanks</div><div><br></div><div>Fran=
cois</div></div></div></body></html>=

--Apple-Mail-604--77080278--