Dan,
Thank you for your detailed comments. Sorry for the delayed response. I was
away on vacation and just got back. Please see my responses below inline.
regards,
suresh
--- Romascanu, Dan (Dan) [EMAIL PROTECTED] wrote:
1. Is the 'strict' SNMP terminology intentionally avoided in Section 4.2
Hello,
I am only a Chinese student.And my English is lame.
So sorry for my lame English,at first.
I found a mistake in rfc2812.I think you could fix this.
At the page 5 of the protocol,
===quotation==
The presence of a prefix is indicated with a
Hello,
The RFC Editor already knows the error in RFC2812 but not in RFC2813.
See http://www.rfc-editor.org/errata.html. Please tell the RFC
Editor about the error in RFC2813.
Please see RFC4234 for the full definition of Augmented BNF.
Section 3.6 explains * .
Thanks
Brian Carpenter
IETF
Hi,
I notice that a new draft of CalDAV has been published
(http://www.ietf.org/internet-drafts/draft-dusseault-caldav-14.txt),
but that the Last Call comments in the email I'm replying to here
(http://www1.ietf.org/mail-archive/web/ietf/current/msg43094.html)
have been ignored.
Now my
Dear all,
as some of you may know, we have conducted some wireless measurements at
the 65th IETF in Dallas. Based on previous feedback, we were looking for
some anomalies in the wireless network. In our measurements we found
different behaviors for different wireless card vendors.
This is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry all to be slightly off topic, but I would like to know if there
are any person on the IETF list who lives in the Pacific Islands or is
from the Pacific Islands (and not from Hawaii...).
I'm vice chairman of the Pacific Islands Chapter of the
Joel,
thank you for your comments and for clarifying how the APs were
deployed. On the Apple clients issue I generally agree with you. We
considered the Apple behavior good relative to the highly congested
environment encountered at the IETF meeting. In this particular
environment most
Greetings,
That makes for an interesting read especially the client hand-off
measurement.
just two observations...
The low dis/re-association rate associated with the apple clients is
described as good, and in the sense that it reduces churn I agree with
that. But if in fact it means you
Julian Reschke wrote:
With respect to draft 14, I notice that the reference to RFC2518bis has
been downgraded to RFC2518 (which I don't object to), but that
references *into* RFC2518 now use broken section numbers (as they
haven't been updated accordingly).
Hi Julian,
I'm sorry but all
On 8/28/06, Bernard Desruisseaux [EMAIL PROTECTED] wrote:
I'm sorry but all references into RFC2518 have been updated accordingly
as far I can tell. Am I missing something?
The interesting point was this one:
There may be more new problems I currently don't have time to check
for, and I'm
Here is a reminder of the BOF scheduling deadlines for San Diego.
There might be some confusion since I just noticed a link to an
obsolete version on the IETF site.
---
If you are expecting to propose a BOF in San Diego, please
note the new scheduling deadlines:
August 7, Monday
The IETF Secretariat is pleased to announce an update to the IETF Email
List Request tool (https://datatracker.ietf.org/public/request_list.cgi).
The tool now allows a user to request that a working-group or
non-working-group mailing list that is hosted at ietf.org be closed. In
addition, if
The IESG has approved the following document:
- 'Common Policy: A Document Format for Expressing Privacy Preferences '
draft-ietf-geopriv-common-policy-11.txt as a Proposed Standard
This document is the product of the Geographic Location/Privacy Working
Group.
The IESG contact persons are
The IESG has received a request from an individual submitter to consider
the following document:
- 'DES Security Implications '
draft-kelly-saag-des-implications-04.txt as an Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.
The IESG has received a request from the Audio/Video Transport WG to
consider the following document:
- 'RTP Payload Format and File Storage Format for the Adaptive Multi-Rate
(AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs '
draft-ietf-avt-rtp-amr-bis-05.txt as a Proposed
A new Request for Comments is now available in online RFC libraries.
RFC 4669
Title: RADIUS Authentication Server MIB for
IPv6
Author: D. Nelson
Status: Standards Track
Date: August 2006
Mailbox:
A new Request for Comments is now available in online RFC libraries.
RFC 4668
Title: RADIUS Authentication Client MIB for
IPv6
Author: D. Nelson
Status: Standards Track
Date: August 2006
Mailbox:
A new Request for Comments is now available in online RFC libraries.
RFC 4671
Title: RADIUS Accounting Server MIB for
IPv6
Author: D. Nelson
Status: Informational
Date: August 2006
Mailbox:
A new Request for Comments is now available in online RFC libraries.
RFC 4670
Title: RADIUS Accounting Client MIB for
IPv6
Author: D. Nelson
Status: Informational
Date: August 2006
Mailbox:
The IESG has received a request from an individual submitter to consider
the following document:
- 'Progressive Posting Rights Supsensions '
draft-carpenter-rescind-3683-01.txt as a BCP
This document abolishes the existing form of indefinite Posting
Rights Action and restores the
20 matches
Mail list logo
