Last night by video link I participated in a press conference that was
arranged by ICANN. I was part of a panel; the rest of the people were
in Las Vegas at the BlackHat conference. Each panel member gave a 3
minute statement, and then the panel responded to questions from the
reporters. I
http://news.yahoo.com/s/afp/20100729/tc_afp/usitinternetsoftwarecrimeicannblackhat
Ole J. Jacobsen
Editor and Publisher, The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972 Mobile: +1 415-370-4628
E-mail: o...@cisco.com URL: http://www.cisco.com/ipj
http://news.yahoo.com/s/afp/20100729/tc_afp/usitinternetsoftwarecrimeicannblackhat
I guess the next report after a noticeable increase of IPv6 deployment
will be something like We made the Internet larger ...
Cheers
___
Ietf mailing list
Ietf@ietf.org
The IETF list is often a place for rants and raves. I have a concern that I
want to raise, but I also want to be constructive about it. I'm hoping my
colleagues will play ball with that.
I am really happy to see the interest and conversation that has been happening
at IETF-77 and IETF-78
Aaron Stone wrote:
Additionally, the requirements to first check via HTTPS, then via
HTTP, and the requirements for identical contents, are not
requirements imposed by RFC 5785 -- though 5785 allows that a
registration ... MAY also contain additional information, ... or
protocol-specific
On 7/29/2010 10:00 PM, Fred Baker wrote:
If we're going to continue this avalanche of ad hoc meetings that we call
Bar BOFs, I would recommend that the Secretariat provide a web page for
requesting them. The title of the web page should be Poorly Planned
Meetings or something like that.
In
Just saying ... too late.
http://trac.tools.ietf.org/bof/trac/wiki/BarBofsIETF78 and predecessors have
been out there for at least a couple of IETFs (like you guys, I'm
exhausted, and in my case, too exhausted to check how many IETFs we've had
such pages, but I know we had a list in Anaheim).
On 2010-07-30 08:47, Dave CROCKER wrote:
On 7/29/2010 10:00 PM, Fred Baker wrote:
If we're going to continue this avalanche of ad hoc meetings that we call
Bar BOFs, I would recommend that the Secretariat provide a web page for
requesting them. The title of the web page should be Poorly
Brian E Carpenter wrote:
I wish it had just been six of us at the bar.
From the BOFettes I participated in in Anaheim, I
got the general impression that the intent of the
get-together was to build support for turning
whatever into a working group - to create yes
votes (like it or not we've
Fred: I had the same experience -- I guess many of us did. Last night I
was at one until 9:20, when I left early to go quickly to another one
where I was able to get a little food while we had a meeting. I quit at
11:45 and it was still going. Tonight I managed to get a slice of pizza
Peter,
I'm not sure if this one is already on your list or not, but I
didn't see it addressed in -08:
I don't think the characterization of SRV-ID as an indirect
(ie. DNS resolved) identifier is correct.
Whether a subject name is indirect or not, depends on the content
of the identifier field
On Jul 30, 2010, at 12:28 AM, Scott Brim wrote:
So I can't complain about the get-togethers of any sort, just that there
wasn't enough time for them. I would like to encourage the use of IETF tools
to announce ad hoc discussions using good teleconferencing tools, e.g. video,
whiteboard,
Total of 97 messages in the last 7 days.
script run at: Fri Jul 30 00:53:02 EDT 2010
Messages | Bytes| Who
+--++--+
7.22% |7 | 6.08% |42865 | o...@cisco.com
6.19% |6 | 5.54% |39064 | d...@dcrocker.net
The IESG has approved the following document:
- 'DHCPv6 options for network boot '
draft-ietf-dhc-dhcpv6-opt-netboot-10.txt as a Proposed Standard
This document is the product of the Dynamic Host Configuration Working Group.
The IESG contact persons are Ralph Droms and Jari Arkko.
A URL
The IESG has approved the following document:
- 'Mailing Lists and Internationalized Email Addresses '
draft-ietf-eai-mailinglist-07.txt as an Experimental RFC
This document is the product of the Email Address Internationalization Working
Group.
The IESG contact persons are Alexey
The IESG has received a request from the TCP Maintenance and Minor
Extensions WG (tcpm) to consider the following document:
- 'Making TCP more Robust to Long Connectivity Disruptions (TCP-LCD)'
draft-ietf-tcpm-tcp-lcd-02.txt as an Experimental RFC
The IESG plans to make a decision in the next
16 matches
Mail list logo