I am needing info on where and how do I place the ANI II digits in the
invite header so the quintum DX 4096 voip gateway that I have will
accurately send the calling ANI and the called ANI as well as the ANI II
digits to the Siemens DCO-CS switch that I have.
Any suggestions would be very
A few issues bother me with the present draft. I'm not on the ietf
list, but saw this on the wg-dav list.
Section 5.1. Application Unique ID (AUID)
If we assume that an application is a program (or collection of
programs working together towards a common goal) then this section
assumes that
Hi Lars,
thanks for the pointer. We are discussing a specific mobility-related
problem: when to
change an IP address which we can discuss at the BOF (and at MobOpts
meeting).
Thanks,
-Rajeev
___
Ietf mailing list
Ietf@ietf.org
Without knowing the specifics of Jon's overrides - I can only say
that those I know of involved poorly written or unclear documents
that Jon was exercising reasonable editorial control over. If you're
saying that we don't want an editor for the series - e.g. just
publish what the IESG
On 7 Jun 2006, at 04:52, Brian E Carpenter wrote:
I wouldn't want to exclude the operational and implementer community
either. I think the phrase used in draft-iab-rfc-editor is probably
the best short form: the Internet research and engineering
community. Note of course that there is no way
All,
As you’re all aware, on 06/06/06 NSS successfully launched IPv6 services for
IETF Web, Mail, and FTP. Following the introduction, NSS received a few
technical questions pertaining to IPv6 services. Below you will find technical
information as it pertains to configuration and
I am personally skeptical about the value of the this experiment.
I am concerned about the long term viability of this particular
format. (I saw a recent note about a postscript document that
supposedly used only core features of postscript, but still could not
be printed on a modern
This draft addresses none of the problems identified the last time it
came around, and I strongly encourage the IESG to say no.
Although I sympathize with the concern that some RFCs would work
better with fancier graphics, PDF isn't a solution to any problem I
understand.
Most importantly, PDF
Joel Halpern's comments (below) are right on target. However, Joel is
rather too polite.
First, I must request that the Internet Draft be retracted in its present
form. Section 4
contains a direct quote from one of my messages. However, the quoted
sentence was taken
brazenly out of
On 6/15/06, Bob Braden [EMAIL PROTECTED] wrote:
I am somewhat astonished that the IESG chose to last call
'this document.
The document does not specify a particular variety of PDF. There are many.
The document does not specify the permitted embedded data formats. PDF
allows raster and vector
* Only HTTP, SMTP, FTP, and DNS traffic are permitted through an IPv6
Native firewall (pings, traceroutes etc. are dropped)
Why? Shouldn't we be prompting good firewall practices?
Droping ICMP was a knee jerk reaction to ICMP echo to
directed broadcast
Harald Alvestrand wrote:
Ted Faber wrote:
On Mon, Jun 12, 2006 at 02:11:19PM +0200, Iljitsch van Beijnum wrote:
The problem with text is that you have to walk through memory and
compare characters. A LOT.
That's not where your code spends its time.
Run gprof(1). The majority
This message is being sent to the IETF mailing list in
accordance with recent requests to notify IETF members of proposals to form
working groups etc in this forum.
The OATH consortium
and RSA recently submitted proposals relating to the provisioning of symmetric
keys.
While the
John Levine wrote:
This draft addresses none of the problems identified the last time it
came around, and I strongly encourage the IESG to say no.
Although I sympathize with the concern that some RFCs would work
better with fancier graphics, PDF isn't a solution to any problem I
The key question is whether there exists a format which is likely to be
sufficiently stable that we won't have to revisit this decision in
another 35 years. All the proposed formats - including PDF, XML, etc. -
are moving targets at this time.
That's why I suggested GIF. Like ASCII, GIF has
Spencer Dawkins wrote:
The key question is whether there exists a format which is likely to be
sufficiently stable that we won't have to revisit this decision in
another 35 years. All the proposed formats - including PDF, XML, etc. -
are moving targets at this time.
That's why I suggested
The IESG has received a request from an individual submitter to consider the
following document:
- 'Proposed Experiment: Normative Format in Addition to ASCII Text '
draft-ash-alt-formats-02.txt as an Experimental RFC
The IESG plans to make a decision in the next few weeks, and solicits
A new Request for Comments is now available in online RFC libraries.
RFC 4552
Title: Authentication/Confidentiality for OSPFv3
Author: M. Gupta, N. Melam
Status: Standards Track
Date: June 2006
Mailbox:[EMAIL
A new Request for Comments is now available in online RFC libraries.
RFC 4562
Title: MAC-Forced Forwarding: A Method for
Subscriber Separation on an Ethernet Access
Network
Author: T. Melsen, S. Blake
A new Request for Comments is now available in online RFC libraries.
RFC 4538
Title: Request Authorization through Dialog Identification
in the Session Initiation Protocol (SIP)
Author: J. Rosenberg
Status: Standards
20 matches
Mail list logo
