On Wed, 1 Nov 2006, Sam Hartman wrote:
I don't believe the new charter of ieprep working group belongs in the
IETF. I understand why we chartered it here, and I believe that by
doing as much work as we have done so far in the IETF, we have done
something useful. We've described the broad
Excerpts from Sam Hartman on Wed, Nov 01, 2006 04:34:20PM -0500:
[I could not find the ITU's liaison to the IETF. Scott, if such
exists, I'd appreciate you forwarding this to them.]
The ITU-T's liaison from SG13 to the IETF is Hui-Lan Lu. CCed.
FYI SG13 is about to send something to the IETF
1. I find the security considerations section to be incomplete. What is
missing is a description of the security risks encountered by the
malicious or accidental mis-configuration of the read-write objects that
are listed. For example ' Changing dot3MpcpAdminState state can lead to
disabling the
This is to let the community know that I am *not* available for
another term as IETF Chair.
This was not a quick decision, and it's due to a combination
of professional and personal circumstances. Also, I will soon
complete a total of ten years in the IAB and IESG combined,
and I believe that is
On Wed, Nov 01, 2006 at 12:10:16AM -0800, Fred Baker wrote:
if routing protocols aren't scary enough for you...
http://money.cnn.com/popups/2006/fortune/scary_tech/index.html
Unexpected failure modes led to the early withdrawal of IPv5
--
Tim
Sam,One of the objectives of the work produced by IEPREP was to lay down the ground work and put together a baseline set of requirements to start with when considering solutions. Our intention was that the baseline then becomes a starting point where more specific requirements can be put forth.
At 12:41 PM 11/2/2006 +0200, Pekka Savola wrote:
On Wed, 1 Nov 2006, Sam Hartman wrote:
I don't believe the new charter of ieprep working group belongs in the
IETF. I understand why we chartered it here, and I believe that by
doing as much work as we have done so far in the IETF, we have
James == James M Polk [EMAIL PROTECTED] writes:
James At 12:41 PM 11/2/2006 +0200, Pekka Savola wrote:
On Wed, 1 Nov 2006, Sam Hartman wrote: I don't believe the
new charter of ieprep working group belongs in the IETF. I
understand why we chartered it here, and I believe
ken == ken carlberg [EMAIL PROTECTED] writes:
ken Sam, One of the objectives of the work produced by IEPREP was
ken to lay down the ground work and put together a baseline set
ken of requirements to start with when considering solutions.
ken Our intention was that the baseline
ken Interestingly enough, the work that you mention below in your
ken original posting...
ken ... rfc-4542, rfc-4411, and draft
ken -ietf-tsvwg-vpn-signal-preemption (along with some other
ken related work) has actually not been done in IEPREP because
ken the group was
On Thu, 2 Nov 2006, James M. Polk wrote:
Having looked at the output of the WG,
it already seems to include a couple of useful framework documents and
about 4 requirements documents.
the framework RFCs are for within a single public domain. The other RFCs are
requirements based.
There
Any chance to move one of hokeyp and MIP6
to a different slot so they are not colliding??
Thanks,
Madjid
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
Total of 51 messages in the last 7 days.
script run at: Fri Nov 3 00:03:02 EST 2006
Messages | Bytes| Who
+--++--+
7.84% |4 | 6.32% |17922 | [EMAIL PROTECTED]
5.88% |3 | 5.62% |15958 | [EMAIL
The IAB is announcing its timeline for the appointment of
a member of the IETF Administrative Oversight Committee
(IAOC), as described in BCP 101 (RFC 4071) and in BCP 113 (RFC 4333).
The IESG and the IAB each select one person for a two-year IAOC
term in alternate years. This year, the IAB
14 matches
Mail list logo
