- Original Message -
From: Sprecher, Nurit (NSN - IL/Hod HaSharon) nurit.sprec...@nsn.com
To: ext t.petch daedu...@btconnect.com; stbry...@cisco.com
Cc: ietf@ietf.org
Sent: Sunday, March 18, 2012 12:07 PM
Tom,
Did Huub and Malcolm represent the ITU in their assessments?
tp
Nurit
You know
Top posting because it fits the Subject well, the details below less so.
There is currently a thread in 6man on
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-uri-zoneid-00.txt
http://www.ietf.org/mail-archive/web/ipv6/current/msg15505.html
on how to put this zoneid into a URI which, given
Your statement that some people's views deserve more weight than other
people's. is even offending...
Still, since there is clearly no consensus in the ITU (and not even
close to consensus), we cannot rely on anything except of a formal
liaison which is approved by the ITU expert with consensus.
--On Tuesday, March 20, 2012 09:24 +0100 t.petch
daedu...@btconnect.com wrote:
There is currently a thread in 6man on
Subject: Re: 6MAN WG Last Call:
draft-ietf-6man-uri-zoneid-00.txt
http://www.ietf.org/mail-archive/web/ipv6/current/msg15505.html
on how to put this zoneid into a URI
Dear all,
let me remind you of the upcoming moderation experiments we are going to
setup in Paris. All the details are at the following URL.
http://ietf83.conf.meetecho.com/index.php/UMPIRE_Project
In brief, we have two moderated sessions: 1) SOC WG (RAI area,
3:10pm-4:10pm slot on
On 2012-03-21 04:11, John C Klensin wrote:
--On Tuesday, March 20, 2012 09:24 +0100 t.petch
daedu...@btconnect.com wrote:
There is currently a thread in 6man on
Subject: Re: 6MAN WG Last Call:
draft-ietf-6man-uri-zoneid-00.txt
Hello,
I continue my support for the codepoint allocation
I agree with Russ's statement in
https://www.ietf.org/ibin/c5i?mid=6rid=49gid=0k1=933k2=62185tid=1331648664
Some people are using the lack of a code point as the reason that
the cannot support the ITU-T document. My approach tells the
The IESG has received a request from the Audio/Video Transport Extensions
WG (avtext) to consider the following document:
- 'Considerations for Deploying the Rapid Acquisition of Multicast RTP
Sessions (RAMS) Method'
draft-ietf-avtext-rams-scenarios-03.txt as an Informational RFC
The IESG
The IESG has received a request from the Audio/Video Transport Extensions
WG (avtext) to consider the following document:
- 'Content Splicing for RTP Sessions'
draft-ietf-avtext-splicing-for-rtp-07.txt as an Informational RFC
The IESG plans to make a decision in the next few weeks, and
The IESG has received a request from the Geographic Location/Privacy WG
(geopriv) to consider the following document:
- 'Geolocation Policy: A Document Format for Expressing Privacy
Preferences for Location Information'
draft-ietf-geopriv-policy-25.txt as a Proposed Standard
This last call
The IESG has received a request from the Session Initiation Protocol Core
WG (sipcore) to consider the following document:
- 'SIP-Specific Event Notification'
draft-ietf-sipcore-rfc3265bis-07.txt as a Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final
The IESG has approved the following document:
- 'SPF Authentication Failure Reporting using the Abuse Report Format'
(draft-ietf-marf-spf-reporting-10.txt) as a Proposed Standard
This document is the product of the Messaging Abuse Reporting Format
Working Group.
The IESG contact persons are
The IESG has approved the following document:
- 'Extensions to DKIM for Failure Reporting'
(draft-ietf-marf-dkim-reporting-16.txt) as a Proposed Standard
This document is the product of the Messaging Abuse Reporting Format
Working Group.
The IESG contact persons are Pete Resnick and Peter
14 matches
Mail list logo
