Under the long-standing IETF policy defined in RFC 2804, I trust
we will not be discussing this draft, or
draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.
Regards
Brian Carpenter
On 30/07/2012 09:26, internet-dra...@ietf.org wrote:
A New Internet-Draft is available from the
Under the long-standing IETF policy defined in RFC 2804, I trust
we will not be discussing this draft, or
draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.
aol
Last week the IAB and the IESG met with the leadership of IEEE 802. One of the
things that was discussed was the IEEE policies for allocating EtherTypes, and
the IESG is considering the attached IESG Statement to implement an IETF policy
that aligns with the IEEE policy.
If you have an
As a reminder, the Internet Society is organizing a briefing panel on Tuesday,
31 July, 11:45am - 12:45pm PDT, in conjunction with IETF 84 in Vancouver:
World IPv6: Launched!
On June 6, 2012, more than 50 access providers and thousands of websites around
the globe joined together in
2804 does not say not to talk about such things - or that such documents should
not be published as RFCs - 2804 says that the IETF will not do standards work
in this area
Scott
On Jul 30, 2012, at 5:04 AM, Brian E Carpenter wrote:
Under the long-standing IETF policy defined in RFC 2804, I
We seem to be doing a lot of talking about the draft.
On Jul 30, 2012, at 9:33 AM, Scott O Bradner wrote:
2804 does not say not to talk about such things - or that such documents
should
not be published as RFCs - 2804 says that the IETF will not do standards work
in this area
Scott
Hey Andrew,
Thanks for following up, and sorry for the lag. Thank goodness for IETF
meetings giving us time to process email :)
Couple of responses inline.
MAJOR:
4.1.
It's not clear what the threat model is that this section is
designed to address. If the zone operator is malicious,
2804 does not say not to talk about such things - or that such documents
should
not be published as RFCs - 2804 says that the IETF will not do standards work
in this area
for those of us who are easily confused, could you differentiate between
working on douments and publishing them as rfcs
Yes, Scott, that is correct, sorry for my poor phrasing.
Brian
On 30/07/2012 17:33, Scott O Bradner wrote:
2804 does not say not to talk about such things - or that such documents
should
not be published as RFCs - 2804 says that the IETF will not do standards work
in this area
Scott
I agree with the comments about 2804.
I do note a lot of April 1 RFCs in the references
though, so maybe its all a joke.
S
On 07/30/2012 06:51 PM, Brian E Carpenter wrote:
Yes, Scott, that is correct, sorry for my poor phrasing.
Brian
On 30/07/2012 17:33, Scott O Bradner wrote:
2804
On Mon, 2012-07-30 at 19:26 +0100, Stephen Farrell wrote:
I agree with the comments about 2804.
I do note a lot of April 1 RFCs in the references
though, so maybe its all a joke.
Gotta be!
S
On 07/30/2012 06:51 PM, Brian E Carpenter wrote:
Yes, Scott, that is correct, sorry for
The IESG has received a request from the Operations and Management Area
Working Group WG (opsawg) to consider the following document:
- 'Problem Statement for the Automated Configuration of Large IP
Networks'
draft-ietf-opsawg-automated-network-configuration-04.txt as
Informational RFC
in
Dear IETFers,
I invite to join us at the bar BoF ITS - IP for Intelligent
Transportation Systems
today 30 july 2012
19h30-20h30 Vancouver at Pacific time
room Plaza C, 2nd floor
email list i...@ietf.org, https://www.ietf.org/mailman/listinfo/its
webex
(I hope not to open some Pandora box or a long thread - my goal is to
make sure there is clarity in the language of the statement)
What 'IETF protocol specification' means here?
Pretty clear it covers protocols defined in IETF standards-track
documents.
Does it also cover protocols defined
Dan:
Only protocol specifications make use of Ethertypes. The statement is intended
to apply to any protocol specification on the IETF Stream (Standards Track RFC,
Informational RFC, or Experimental RFC) that needs to allocate a new Ethertype.
Russ
On Jul 30, 2012, at 5:20 PM, Romascanu,
Today at IETF 84 in Vancouver, Lynn St. Amour and I announced the creation of
the Open Internet Endowment and its initial campaign focused on ensuring the
IETF's long-term financial health and continued independence. The web site is
up and running. It offers more information and accepts
I have just posted the draft cited below, to adjust the NomCom
eligibility rules to make the following change:
RFC 3777 excludes from eligibility as NomCom volunteers:
- members of the ISOC Board of Trustees
- sitting members of the IAB
- sitting members of the IESG
The IAOC did not
Sees reasonable. While you are at it, you might complete the I* with IANA...
Thanks,
Donald
=
Donald E. Eastlake 3rd +1-508-333-2270 (cell)
155 Beaver Street, Milford, MA 01757 USA
d3e...@gmail.com
On Mon, Jul 30, 2012 at 9:04 PM, Barry Leiba
Last week the IAB and the IESG met with the leadership of IEEE 802. One of the
things that was discussed was the IEEE policies for allocating EtherTypes, and
the IESG is considering the attached IESG Statement to implement an IETF policy
that aligns with the IEEE policy.
If you have an
A new IETF non-working group email list has been created.
List address: lami...@ietf.org
Archive: http://www.ietf.org/mail-archive/web/laminar/
To subscribe: https://www.ietf.org/mailman/listinfo/laminar
Purpose: This list is for discussing the Laminar TCP and how to proceed
with it, through
Today at IETF 84 in Vancouver, Lynn St. Amour and I announced the creation of
the Open Internet Endowment and its initial campaign focused on ensuring the
IETF's long-term financial health and continued independence. The web site is
up and running. It offers more information and accepts
The NomCom 2012-2013 Call for Volunteers is nearing its conclusion.
If you are considering volunteering to participate in the 2012-2013
NomCom, please volunteer soon. Individuals willing to serve on this
year's NomCom must send email to nomcom-ch...@ietf.org on or before
Sunday, August 5.
22 matches
Mail list logo
