I'd like to second that. Great job!
dbh
-Original Message-
From: Harald Alvestrand [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 23, 2006 9:58 PM
To: ietf@ietf.org
Subject: An absolutely fantastic wireless IETF
Just wanted to state what's obvious to all of us by now:
This
If I remember correctly, we only limit the number of suthors on the
first page of the document.
It is perfectly acceptable to list a longer set of names inside the
document in an contributors section.
I also have concerns about who should be listed as an author and
have copyrights when a work
Overflows in Kerberos
Authenticated Services
Vulnerability Note VU#836088 Multiple vendors' email content/virus
scanners do not adequately check message/partial MIME entities
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: Steven M
:[EMAIL PROTECTED]
Sent: Monday, June 05, 2006 8:21 PM
To: David Harrington
Cc: [EMAIL PROTECTED]; ietf@ietf.org
Subject: Re: Best practice for data encoding?
On Mon, 5 Jun 2006 20:07:24 -0400, David Harrington
[EMAIL PROTECTED] wrote:
Hi
The security problems identified in
http
to the authors and contributors and to others who
want to ask those authors for permissions to do non-IETF things, or if
the IETF decides it needs the rights to transfer rights to others for
non-IETF purposes.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original
as particular criteria for measuring
effectiveness. The criteria seem to miss the whole point of our
working on standards.
I do not believe it would be a worthwhile use of community resources
to run this experiment as designed.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED
of the design, than for a reader not involved in working on the
design.
I fully agree that, for the reasons you give, using such
pretty diagrams as normative would generally be a problem.
David
Harrington[EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED]
From: Stewart Bryant
[mailto
Hi,
I believe the rule was applied to the Entity MIB and the RMONMIB work,
IIRC.
dbh
-Original Message-
From: Henning Schulzrinne [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 13, 2006 9:02 AM
To: Joel M. Halpern
Cc: ietf@ietf.org
Subject: Re: Comments on
for the
mailing list to see what was discussed and decided. I do not think
the chair should be allowed to evade this responsibility by simply
posting a quick summary and the raw jabber logs to the mailing list as
the official minutes.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED
Why not start everything at Experimental, and if it gains market
success then it moves to Full.
dbh
-Original Message-
From: Nelson, David [mailto:[EMAIL PROTECTED]
Sent: Friday, July 21, 2006 10:03 AM
To: IETF Discussion
Subject: RE: netwrk stuff
Dave Crocker writes...
The
Is there any IPR that needs to be disclosed related to such a list?
dbh
-Original Message-
From: Harald Tveit Alvestrand [mailto:[EMAIL PROTECTED]
Sent: Friday, February 02, 2007 10:55 AM
To: Steven M. Bellovin; Dave Cridland
Cc: Dave Aronson; IETF-Discussion
Subject: Re:
Hi,
Yup.
Trying to figure out how to publish this in an internet-draft has been
challenging to say the least.
(publishing the xml2rfc template in an xml2rfc document is even more
challenging!)
The template, in both text and xml2rfc format, has been available on
the OPS website since July.
interesting things to see. I rate
it as one of my favorite cities in Europe.
So I agree that Prague is very survivable.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: Dave Crocker [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 07
Maybe they should sell the liquor in small transparent baggies.
dbh
-Original Message-
From: Mark Andrews [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 14, 2007 7:40 PM
To: [EMAIL PROTECTED]
Cc: IETF discussion list
Subject: Re: Warning - risk of duty free stuff being
not look acceptable
please identify your objections, preferably with suggested text that
would make it acceptable.
Thanks,
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
co-chair, Syslog WG
___
Ietf mailing list
Ietf@ietf.org
https://www1
claiming consistency with RFC2828(bis). It is already hard to verify
that MUST/SHOULD/MAY are used correctly per RFC2119, and RFC2828bis
has 300 pages of definitions, re-definitions, and phrases.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED
) Section three uses must where MUST would seem appropriate.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
of open source implementations that place limitations on implementing
our worldwide specifications in products of all types.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman
. Halpern
+1
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
I think the complaints would simply be slurred more, and we might have
to worry about lynch mobs (which would remind me of the reasonableness
of this discussion so far).
dbh
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dave Crocker
Sent:
Hi,
I think asking attendees during registration which sessions they
intend to attend and building a conflict matrix would be the simplest
approach. Of course, attendee conflicts matter less than ADs, chairs,
and presenter conflicts.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL
and digital signatures.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Samuel Weiler
Sent: Friday, April 11, 2008 6:49 PM
To: [EMAIL PROTECTED]
Subject: [secdir] Assignments for April
think this is something the SEC ADs should be considering as well.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
___
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
Hi,
I read this document. On a quick read, this seemed very reasonable.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of The IESG
Sent: Wednesday, April 16, 2008 8:17 AM
?
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
___
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED
. But the community that has attended such discussions of
the suitability of different languages for the task at hand has
reached rough consensus and developed multiple implementations of
running code for this proposed direction forward.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL
no better than any other proposal,
so it was posted to NGO for further community discussion.
Apr08: The IESG secretary announced a WG review for Netconf Data
Modeling Language to the IETF mailing list.
I hope this is helpful. Let me kniw if I can help further.
David Harrington
[EMAIL PROTECTED
Hi,
The Trust has analyzed the advantages, and you included the advantages
in your post.
Has the Trust also analyzed any potential disadvantages? Can you tell
us those as well?
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL
Hi,
I support this experiment. Why short sessions? Why not longer
sessions?
In my experience, Friday sessions are invaluable for having working
sessions rather than status sessions, and Friday sessions have been
preferred in some WGs as a way to get real f2f time for engineering.
David
the
IETF process.
I would rather continue to use RFC2026/3978 rules.
David Harrington
dbharring...@comcast.net
ietf...@comcast.net
dharring...@huawei.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
concerns.
David Harrington
dbharring...@comcast.net
ietf...@comcast.net
dharring...@huawei.com
___
secdir mailing list
sec...@ietf.org
https://www.ietf.org/mailman/listinfo/secdir
___
Ietf mailing list
Ietf
Hi Douglas,
For the most part, I really like the new security considerations
section in 09. I found it far more enlightening (and even
interesting). Thanks.
I usually look for security considerations in a form that points out
the threats and how they are mitigated (or can be mitigated by
point well enough to take action, and, as he points out, the
document says it is not trying to solve the problem he raises.
[dbh: no action taken.]
draft-ietf-opsawg-operations-and-management-08 has been posted.
David Harrington
dbharring...@comcast.net
ietf...@comcast.net
dharring...@huawei.com
Hi,
Personally, I would like to see deltas kept for updated charters,
especially the milestone information, so we can go back and find out
how timely a WG has achieved its completed objectives.
When I try to determine whether participating in a WG seems justified,
one thing I want to know is
Hi,
We are running multiple experiments.
One is automated registration.
One is RFID.
Another is charging for subsets of attendance.
Maybe we should have an RFID reader/recorder at the door to each
session, and to send bills to people based on what they actually
attend (plus a base fee).
Hi,
Some social events have attendance limits. Are day-pass holders
allowed to attend the social? Do full-week registrants get preference
for social tickets?
dbh
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
If part of the purpose of the one-day pass is to let new attendees
understand how the IETF works, why don't we make attendance in the
newcomers' tutorial free - no paid attendance required, just
registration (for planning purposes).
I would rather have newcomers learn from the newcomers' training
Looks good to me.
I have concerns about #6, since it is fairly common that we run light
on food during the reception. And if there are limits on the
reception, then I think it reaosnable to favor those who paid for the
full week. But I can support the experiment.
Will One Day Pass first-timers
code have
been considered. None of this has been documented, so a reader cannot
know whether these have been considered and not documented, or simply
overlooked.
I do not think this document is ready for publication as an RFC.
David Harrington
dbharring...@comcast.net
ietf...@comcast.net
dharring
Hi,
As part of declaring IPv6 a full standard, would we also declare IPv4
obsolete or Historic?
dbh
-Original Message-
From: ietf-boun...@ietf.org [mailto:ietf-boun...@ietf.org] On
Behalf Of Iljitsch van Beijnum
Sent: Friday, September 11, 2009 11:25 AM
To: IETF Discussion
indoors.
I think the level of poluution in Beijing is a valid concern when
evaluating venues.
David Harrington
dbharring...@comcast.net
ietf...@comcast.net
dharring...@huawei.com
--
Randall Gellens
Opinions are personal;facts are suspect;I speak for
myself only
-- Randomly
it include multiple VSS options? The second
paragraph of 6 says that
is not allowed.
David Harrington
dbharring...@comcast.net
ietf...@comcast.net
dharring...@huawei.com
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo
Hi,
part of the justification is to have the BOF early in the week so
people can discuss it during the week.
dbh
-Original Message-
From: iesg-boun...@ietf.org [mailto:iesg-boun...@ietf.org] On
Behalf Of Richard L. Barnes
Sent: Monday, November 08, 2010 10:29 AM
To: ietf@ietf.org
core protocol ONLY works with an IPv4 NAT'd transport, I
believe you will get pushback.
The solution should also be able to work in other environments, such
as an un-NAT'd IPv6 environment.
David Harrington
On Mon, Nov 15, 2010 at 12:19 AM, Hadriel Kaplan
hkap...@acmepacket.com wrote:
Hi
Hi,
This review did not get copied to IESG or IETF lists.
David Harrington
Director, IETF Transport Area
ietf...@comcast.net (preferred for ietf)
dbharring...@huaweisymantec.com
+1 603 828 1401 (cell)
-Original Message-
From: Woundy, Richard [mailto:richard_wou...@cable.comcast.com
suggest you COULD design the web security standard first, and then
design HTTP 2.0 to take the updated web security standards into
consideration. Web security will be easier if it doesn't need to somehow
fit into an HTTP 2.0 that didn't consider a viable security approach
up-front.
--
David
Point taken.
--
David Harrington
Director, Transport Area
Internet Engineering Task Force (IETF)
ietf...@comcast.net
+1-603-828-1401
On 2/22/12 12:31 PM, Paul Hoffman paul.hoff...@vpnc.org wrote:
The earnest calls for better authentication on this thread appear to
ignore the fact
similar expectations regarding ipfix IEs.
--
David Harrington
Internet Engineering Task Force (IETF)
ietf...@comcast.net
+1-603-828-1401
On 5/25/12 6:30 PM, Cullen Jennings flu...@iii.ca wrote:
WIll the IPFIX and MIB work also be usable by v4 to v4 NATs?
On May 15, 2012, at 11:53 AM, IESG
it just because we want to see vendors use
our protocols; that is a market-driven decision to be made by vendors
based on customer demand.
--
David Harrington
Internet Engineering Task Force (IETF)
ietf...@comcast.net
+1-603-828-1401
On 7/19/12 8:51 AM, Simon Perreault simon.perrea
current
implementations - that would represent best CURRENT practices.
--
David Harrington
Internet Engineering Task Force (IETF)
ietf...@comcast.net
+1-603-828-1401
On 7/19/12 8:51 AM, Simon Perreault simon.perrea...@viagenie.ca wrote:
Behaviers, PCPers,
During IESG review of draft-ietf
bit on the wishful thinking side of things. So, I could
understand if the IESG wanted to ask behave to spend a little more time
on the question.
+1 (or ask sunset4 to spend a little more time on the question).
David Harrington
ietf...@comcast.net
+1-603-828-1401
+1
--
David Harrington
ietf...@comcast.net
+1-603-828-1401
On 8/2/12 12:59 PM, Romascanu, Dan (Dan) droma...@avaya.com wrote:
Hi,
The OPSAWG/OPSAREA open meeting this afternoon has an item on the agenda
concerning the revision of RFC1052 and discussing a new architecture for
management
that Wes and
Martin re-established the dinners. That's a good thing.
Hope this helps,
David Harrington
dbharring...@comcast.net
+1-603-828-1401
subset used for SMI.
There are tools to validate against the more current ASN.1 standard.
I'm not sure how much current ASN.1 is used in IETF documents, but if it
is, then you might want to validate it.
I think there is very little current ASN.1 usage in IETF documents.
--
David Harrington
ietf
Hi,
I read this document. On a quick read, this seemed very reasonable.
David Harrington
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of The IESG
Sent: Wednesday, April 16, 2008 8:17 AM
55 matches
Mail list logo
