From admin@computeradmin.org Wed Sep 1 20:26:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19518; Wed, 1 Sep 2004 20:26:50 -0400 (EDT) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2fTY-0000rS-Ls; Wed, 01 Sep 2004 20:29:17 -0400 Received: from [200.121.110.198] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1C2fQa-00030f-T8; Wed, 01 Sep 2004 20:26:25 -0400 Received: from or4c.4ng6tow.net [143.212.60.13] by 65.246.255.50 with ESMTP id 74389459; Thu, 02 Sep 2004 02:28:34 +0100 Message-ID: <9dqedp$211e$1$1ta3f50--q88@4d2ph> From: "Administrator" To: pana@ietf.org Subject: Attention All Nonprofit Organizations: Members and Staff Date: Thu, 02 Sep 04 02:28:34 GMT X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 6.00.2600.0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="3434D40CB.3823E_E0" X-Spam-Score: 36.9 (++++++++++++++++++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 00e94c813bef7832af255170dca19e36 This is a multi-part message in MIME format. --3434D40CB.3823E_E0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Attention All Nonprofit Organizations: Members and Staff You Must Respond By 5 P.M. Thursday, September 2, 2004. Through a special arrangement, Avtech Direct is offering a limited allotment of BRAND NEW, top of-the-line, name-brand desktop computers at more than 50% off MSRP to all Nonprofit Members and Staff who respond to this message before 5 P.M., Thursday, September 2, 2004. All desktop are brand-new, packed in their original boxes, and come with a full manufacturer's warranty plus a 100% satisfaction guarantee. These professional grade Desktops are fully equipped with 2004 next generation technology, making these the best performing computers money can buy. Avtech Direct is offering these feature rich, top performing Desktop Computers with the latest Intel technology at an amazing price to all who call: 1-800-884-9510 by 5 P.M. Thursday, September 2, 2004 The fast and powerful AT-2400 series Desktop features: * Intel 2.0Ghz Processor for amazing speed and performance * 128MB DDR RAM, --- Upgradeable to 1024 * 20 GB UDMA Hard Drive, --- Upgradeable to 80 GB * 52X CD-Rom Drive, --- Upgradeable to DVD/CDRW * 1.44 Floppy disk drive * Next Generation Technology * ATI Premium video and sound * Full Connectivity with Fax modem/Lan/IEE 1394/USB 2.0 * Soft Touch Keyboard and scroll mouse * Internet Ready * Network Ready * 1 Year parts and labor warranty * Priority customer service and tech support MSRP $699 ........................................ Your Cost $297 How to qualify: 1. You must be a Member, Staff or Associate of a Nonprofit. 2. All desktop computers will be available on a first come first serve basis. 3. You must call 1-800-884-9510 by 5 P.M. Thursday, September 2, 2004 and we will hold the desktops you request on will call. 4. You are not obligated in any way. 5. 100% Satisfaction Guaranteed. Call Avtech Direct 1-800-884-9510 before 5 P.M. Thursday, September 2, 2004 Visit our website at http://www.avtechdirectcomputers.com If you wish to unsubscribe from this list, please go to: http://www.computeradvice.org/unsubscribe.asp Avtech Direct 22647 Ventura Blvd., Suite 374 Woodland Hills, CA 91364 --3434D40CB.3823E_E0-- From ywenu@msn.com Wed Sep 1 20:36:40 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20085; Wed, 1 Sep 2004 20:36:40 -0400 (EDT) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2fd3-0001YV-OI; Wed, 01 Sep 2004 20:39:07 -0400 Received: from [211.240.111.220] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1C2fah-0005LZ-8v; Wed, 01 Sep 2004 20:36:40 -0400 Received: from 90.192.60.32 by 65.246.255.50; Thu, 02 Sep 2004 05:31:07 +0400 Message-ID: From: "Marie Tipton" Reply-To: "Marie Tipton" To: pilc-admin@ietf.org Subject: Pilc-admin Here's 0prah's secret t0 l@@king y0ung Date: Thu, 02 Sep 2004 07:29:07 +0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--7323593470600581938" X-Priority: 1 X-CS-IP: 120.68.64.246 X-Spam-Score: 27.7 (+++++++++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3 ----7323593470600581938 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable
As se= en on NBC, CBS, and CNN, and even Oprah! The h= ealth
discovery tha= t actually reverses aging while burning fat, <= br> without dieti= ng or exercise! This proven discovery has even
been reported on by major Science Journals.
Forget aging and dieting forever! And It= 's Guaranteed!

* Reduce body fat and build lean muscle WITHOUT EXERCISE!
* Enhance sexual performance
* Remove wrinkles and cellulite
* Lower blood pressure and improve cholesterol profile
* Improve sleep, vision and memory
* Restore hair color and growth
* Strengthen the immune system
* Increase energy and cardiac output
* Turn back your body's biological clock 10-20 years in 6 months!!= !

Shop here for= HGH





Smart Way to lose the weight!
Revolutionary Diet Patch
No Pills
No Exercise
No Starving
Natural and Safe
Guaranteed Results
Lose 3 to 8 pounds each week
Increased Energy
Decreased Food Cravings
Boosted Metabolism
It Works!

Shop= here for Diet Patch












Why was this email sent to you? At some point you registered or made a purchase on a Web site with privacy policies explaining= that they may share your information with partners who will send you valuable= offers from time to time.

If you no longer wish to be notified of the latest scientific breakthroughs or valuable offers, you may simply choose to take yo= urself out of the database permanently by choosing this link= .
----7323593470600581938-- From IKNMNVRRB@rogers.com Sat Sep 4 04:09:55 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01646; Sat, 4 Sep 2004 04:09:55 -0400 (EDT) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C3VfE-000484-8a; Sat, 04 Sep 2004 04:12:49 -0400 Received: from 82-40-10-27.cable.ubr02.uddi.blueyonder.co.uk ([82.40.10.27]) by mx2.foretec.com with smtp (Exim 4.24) id 1C3VcQ-0004b5-Ru; Sat, 04 Sep 2004 04:09:55 -0400 X-Message-Info: QLTiQEJ9jisBNGiLOr290YDFoq244+DXUv8jeeX Received: from vllssuyz2.attglobal.net (139.220.45.70) by rxh26-gls7.attglobal.net with Microsoft SMTPSVC(5.0.2195.6824); Sat, 04 Sep 2004 14:00:12 +0500 Received: from Ezrajvw810ork8nb989a (70.16.120.218) by sjziugfglsayc879.attglobal.net (InterMail vM.5.01.06.05 092-167-950-855-553-951900) with SMTP id <1111132094355362.YHGV798.tpvysdk353.attglobal.net@montztx8o43px980bvi> for ; Sat, 04 Sep 2004 12:05:12 +0300 Message-ID: <0576lci6xs34215$411781237$dx85eo177@Ezralc1yq0lz07sme> From: "Alfred Ochoa" To: Subject: RE: Ch33p ph@armacii site! Cluick here now! madam Date: Sat, 04 Sep 2004 10:00:12 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--19308909093261849" X-Spam-Score: 12.5 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 ----19308909093261849 Content-Type: text/html; Content-Transfer-Encoding: 7Bit Hi and welcome to our phaarmecy!

One of the things we offer to you, as a aprreciated costomer, is a big variety,
combined with good and honest prjces.
All the medjcatjons you need with cheep prjcees !

We got all original brands and geneeric:
vjagra, cjaljs, lavjtra, xanaax, valioom and a lot more!


http://quispoll.com/100/index.php?ai=7707

consider gerbil m-e auff lincoln gettysburg
%RND2_SENTENCE[2-5]
%RND2_SENTENCE[2-5]
%RND2_SENTENCE[2-5]
%RND2_SENTENCE[2-5]
%RND2_SENTENCE[2-5] ----19308909093261849-- From owner-ietf-provreg@cafax.se Wed Sep 8 13:11:10 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28387 for ; Wed, 8 Sep 2004 13:11:10 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5629-0004vy-PY for provreg-archive@ietf.org; Wed, 08 Sep 2004 13:15:02 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i88GujDT001714 for ; Wed, 8 Sep 2004 18:56:45 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i88GujO8020413 for ietf-provreg-outgoing; Wed, 8 Sep 2004 18:56:45 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i88Gui34008764 for ; Wed, 8 Sep 2004 18:56:44 +0200 (MEST) Received: from vsvapostalgw3.vcorp.ad.vrsn.com (vsvapostalgw3.vcorp.ad.vrsn.com [10.170.12.61]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i88GsRop017674 for ; Wed, 8 Sep 2004 12:54:27 -0400 (EDT) Received: by vsvapostalgw3.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Wed, 8 Sep 2004 12:56:38 -0400 Message-ID: <07241BB00D6943429D073403834717CE027E3B@dul1wnexm04.vcorp.ad.vrsn.com> From: "Gould, James" To: "'ietf-provreg@cafax.se'" Subject: [ietf-provreg] Support for multiple status values in the Domain Registry Grace P eriod Mapping Date: Wed, 8 Sep 2004 12:56:38 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C495C4.CE718010" Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.5 (/) X-Scan-Signature: 8b6657e60309a1317174c9db2ae5f227 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C495C4.CE718010 Content-Type: text/plain All, Currently the Domain Registry Grace Period Mapping only supports specifying a single rgp:statusType in the respDataType. I believe should be changed to . The issue is that a domain might be in multiple grace periods and therefore returning multiple grace period statuses should be allowed. For example, a Domain can be created and renewed one day later, which means that the domain is in the addPeriod and the renewPeriod. Does anyone have a similar issue or have an issue with supporting multiple RGP statuses? JG James F. Gould VeriSign Naming and Directory Services jgould@verisign.com This message is intended for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized use, distribution, or disclosure is strictly prohibited. If you have received this message in error, please notify sender immediately and destroy/delete the original transmission ------_=_NextPart_001_01C495C4.CE718010 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

All,

 

Currently the =
Domain Registry Grace Period Mapping only supports =
specifying a single rgp:statusType in the respDataType.  I believe =
<element name=3D"rgpStatus" =
type=3D"rgp:statusType"/> should be changed to <element =
name=3D"rgpStatus" type=3D"rgp:statusType" =
maxOccurs=3D"7 or unbounded"/>.  The =
issue is that a domain might be in multiple grace periods and therefore =
returning multiple grace period statuses should be allowed.  For =
example, a Domain can be created and renewed one day later, which means =
that the domain is in the addPeriod and the renewPeriod.  =

 

Does anyone have a similar issue or have an issue = with supporting multiple RGP statuses? 

 

 

JG

 

James F. Gould

VeriSign = Naming and Directory Services

jgould@verisign.com

 

 

This message is intended for the use of the individual or = entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any = unauthorized use, distribution, or disclosure is strictly prohibited. If you have = received this message in error, please notify sender immediately and = destroy/delete the original transmission

 

------_=_NextPart_001_01C495C4.CE718010-- From rklioh@msn.com Wed Sep 8 18:08:52 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26381; Wed, 8 Sep 2004 18:08:51 -0400 (EDT) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C5AgH-0004Lb-4i; Wed, 08 Sep 2004 18:12:46 -0400 Received: from tconl8829.tconl.com ([204.26.88.29]) by mx2.foretec.com with smtp (Exim 4.24) id 1C5AcW-0007JI-Eu; Wed, 08 Sep 2004 18:08:52 -0400 Received: from 13.165.131.56 by 204.26.88.29; Thu, 09 Sep 2004 00:04:50 +0100 Message-ID: From: "Jed Pate" Reply-To: "Jed Pate" To: proceedings@ietf.org Subject: Proceedings here is H G H - the f0untain of y0uth Date: Wed, 08 Sep 2004 16:00:50 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--61942433318411548" X-IP: 104.228.10.60 X-Spam-Score: 32.7 (++++++++++++++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3 ----61942433318411548 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable
As se= en on NBC, CBS, and CNN, and even Oprah! The h= ealth
discovery tha= t actually reverses aging while burning fat, <= br> without dieti= ng or exercise! This proven discovery has even
been reported on by major Science Journals.
Forget aging and dieting forever! And It= 's Guaranteed!

* Reduce body fat and build lean muscle WITHOUT EXERCISE!
* Enhance sexual performance
* Remove wrinkles and cellulite
* Lower blood pressure and improve cholesterol profile
* Improve sleep, vision and memory
* Restore hair color and growth
* Strengthen the immune system
* Increase energy and cardiac output
* Turn back your body's biological clock 10-20 years in 6 months!!= !

Shop here for= HGH





Smart Way to lose the weight!
Revolutionary Diet Patch
No Pills
No Exercise
No Starving
Natural and Safe
Guaranteed Results
Lose 3 to 8 pounds each week
Increased Energy
Decreased Food Cravings
Boosted Metabolism
It Works!

Shop= here for Diet Patch












Why was this email sent to you? At some point you registered or made a purchase on a Web site with privacy policies explaining= that they may share your information with partners who will send you valuable= offers from time to time.

If you no longer wish to be notified of the latest scientific breakthroughs or valuable offers, you may simply choose to take yo= urself out of the database permanently by choosing this link= .
----61942433318411548-- From tech@computeradmin.org Tue Sep 14 18:03:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27320; Tue, 14 Sep 2004 18:03:21 -0400 (EDT) Received: from [61.145.73.222] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1C7LTT-0002Wu-Bb; Tue, 14 Sep 2004 18:08:33 -0400 Received: from zbkf.au7bu.net (HELO ndsqe) [156.147.119.140] by 132.151.6.1 id <2780569-57643>; Wed, 15 Sep 2004 02:57:44 +0400 Message-ID: <0e257h75go-aguh8t34--$r@tdrh92dgrqsdd2> From: "Administrator" To: pim@ietf.org Subject: Attention All Nonprofit Organizations: Members, Staff and Associates Date: Wed, 15 Sep 04 02:57:44 GMT X-Priority: 1 X-MSMail-Priority: High X-Mailer: eGroups Message Poster MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="3F__.E3B5.BCC" X-Spam-Score: 25.7 (+++++++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 00e94c813bef7832af255170dca19e36 This is a multi-part message in MIME format. --3F__.E3B5.BCC Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Attention All Nonprofit Organizations: Members, Staff and Associates: You Must Respond By 5 P.M. Thursday, September 16, 2004. Through a special arrangement, Avtech Direct is offering a limited allotment of BRAND NEW, top of-the-line, name-brand desktop computers at more than 50% off MSRP to all Nonprofit Members and Staff who respond to this message before 5 P.M., Thursday, September 16, 2004. All desktop are brand-new, packed in their original boxes, and come with a full manufacturer's warranty plus a 100% satisfaction guarantee. These professional grade Desktops are fully equipped with 2004 next generation technology, making these the best performing computers money can buy. Avtech Direct is offering these feature rich, top performing Desktop Computers with the latest Intel technology at an amazing price to all who call: 1-800-884-9510 by 5 P.M. Thursday, September 16, 2004 The fast and powerful AT-2400 series Desktop features: * Intel 2.0Ghz Processor for amazing speed and performance * 128MB DDR RAM, --- Upgradeable to 1024 * 20 GB UDMA Hard Drive, --- Upgradeable to 80 GB * 52X CD-Rom Drive, --- Upgradeable to DVD/CDRW * 1.44 Floppy disk drive * Next Generation Technology * ATI Premium video and sound * Full Connectivity with Fax modem/Lan/IEE 1394/USB 2.0 * Soft Touch Keyboard and scroll mouse * Internet Ready * Network Ready * 1 Year parts and labor warranty * Priority customer service and tech support MSRP $699 ........................................ Your Cost $297 How to qualify: 1. You must be a Member, Staff or Associate of a Nonprofit. 2. All desktop computers will be available on a first come first serve basis. 3. You must call 1-800-884-9510 by 5 P.M. Thursday, September 16, 2004 and we will hold the desktops you request on will call. 4. You are not obligated in any way. 5. 100% Satisfaction Guaranteed. Call Avtech Direct 1-800-884-9510 before 5 P.M. Thursday, September 16, 2004 Visit our website at http://www.avtechdirectcomputers.com If you wish to unsubscribe from this list, please go to: http://www.computeradvice.org/unsubscribe.asp Avtech Direct 22647 Ventura Blvd., Suite 374 Woodland Hills, CA 91364 --3F__.E3B5.BCC-- From tech@computeradmin.org Tue Sep 14 21:08:01 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12652; Tue, 14 Sep 2004 21:08:01 -0400 (EDT) Received: from [202.96.189.45] (helo=132.151.6.1 ident=CacheFlow Server) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1C7OMB-0006Pd-WE; Tue, 14 Sep 2004 21:13:14 -0400 Received: from [116.184.178.207] by 132.151.6.1; Tue, 14 Sep 2004 20:12:23 -0600 Message-ID: From: "Administrator" To: nemo-admin@ietf.org Subject: Attention All Nonprofit Organizations: Members and Staff Date: Tue, 14 Sep 04 20:12:23 GMT X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 6.00.2462.0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="BE_C4_44_F.438A0_F__" X-Spam-Score: 35.1 (+++++++++++++++++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8 This is a multi-part message in MIME format. --BE_C4_44_F.438A0_F__ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Attention All Nonprofit Organizations: Members and Staff You Must Respond By 5 P.M. Thursday, September 16, 2004. Through a special arrangement, Avtech Direct is offering a limited allotment of BRAND NEW, top of-the-line, name-brand Notebook computers at more than 50% off MSRP to all Nonprofit Members and Staff who respond to this message before 5 P.M., Thursday, September 16, 2004. All Notebooks are brand-new, packed in their original boxes, and come with a full manufacturer's warranty plus a 100% satisfaction guarantee. These professional grade Notebooks are lightweight and fully Equipped with the Next Generation WiFi technology, making these The very best performing computers that money can buy. Avtech Computers is offering these feature rich, top performing Notebooks With the latest Wireless technology at an amazing price To all who call: : 1-800-318-1388 by 5 P.M. Thursday, September 16, 2004 AT-1000S Notebook Series- The ultimate combination of innovative mobile features and practical value= . * 1 Giga Pro Transmeta Crusoe Mobile CPU for incredible power * 128 MB Super Fast DDR SDRAM at 400MHz (Upgradeable to 256 MB) * 20 GB ATA100 Hard Drive (Upgradeable to 30GB ATA100 Hard Drive) * CD-Rom Drive (Upgradeable to DVD/CDRW) * Next Generation 802.11 Wireless Technology for total WiFi freedom * 14.1 XGA TFT Ultra Sharp Liquid Display * Premium Sound and Video * Enhanced Front Stereo Speakers * Total Connectivity 56K V.90 Performance Pro Fax Modem * Integrated High Performance Intel=FFFFFFAE 10/100 LAN Gigabit Ethernet * TV-Out Port with S-Video and USB 2.0 Ports * Soft Touch Keyboard * Programmable Synaptics Touchpad Mouse * Internet and Network Ready * Extra Long Life Battery Pack * Full Range 160Watt AC Adapter * 1 Year parts and labor warranty * Priority Customer Service and Toll Free Technical Support * Latest Qualified Drivers Installed MSRP $1299 .......................................... Your Cost $597 Avtech/ASUS AT-2500 The AT-2500, using the latest technology by ASUS, achieves a perfect blend= of style and performance at a remarkable price. Quantities for this super fast and extremely reliable notebook computer are strictly limited to supplies on hand. The AT-2500 Notebook by ASUS Features: * 2.0 GHz Intel Processor * 15.0" SXGA+ active matrix color Display for an amazing picture * ASUS ADTD II heat dissipation technology for a quieter computer that consumes less power * 20 GB Hard Drive with Ultra DMA100 support. (Upgradeable to/80 GB) * 256 MB Dual Channel DDR SDRam (Upgradeable to 1024MB) * CDRW / DVD combo drive (Upgradeable to DVD RW) * SoundBlaster Pro audio Build-in stereo speakers * 5 USB 2.0 ports, 56K V90 Fax Modem, 10/100BaseT PCI LAN on board * Serial port, Parallel port, TV Out, S-Video, IEEE 1394 port Fire wire, SIR port, PCMCIA 2.1 * Full size 88key Keyboard with MS-Windows function keys * Built-in Touch pad pointing device ASUS Power4 Gear Technology effectively adjusts CPU & LCD to maximize battery life * 8 cell Long Life Smart Battery * Advanced Asus Step power management technology * 2 year ASUS Warranty MSRP $1999 .......................................... Your Cost $997 How to qualify: 1. You must be a Member, Staff or Associate of a Nonprofit. 2. All desktop computers will be available on a first come first serve basis. 3. You must call 1-800-318-1388 by 5 P.M. Thursday, September 16, 2004 and we will hold the computers you request on will call. 4. You are not obligated in any way. 5. 100% Satisfaction Guaranteed. Call Avtech Direct 1-800-318-1388 before 5 P.M. Thursday, September 16, 2004 Visit our website at http://www.avtechdirectcomputers.com If you wish to unsubscribe from this list, please go to: http://www.computeradvice.org/unsubscribe.asp Avtech Direct 22647 Ventura Blvd., Suite 374 Woodland Hills, CA 91364 --BE_C4_44_F.438A0_F__-- From pmlnndb@hotmail.com Thu Sep 23 12:21:05 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27115; Thu, 23 Sep 2004 12:21:05 -0400 (EDT) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAWS2-0003FI-7v; Thu, 23 Sep 2004 12:28:11 -0400 Received: from vdsl-130-13-138-163.phnx.qwest.net ([130.13.138.163]) by mx2.foretec.com with smtp (Exim 4.24) id 1CAWLA-0007jd-DD; Thu, 23 Sep 2004 12:21:04 -0400 Received: from 125.153.246.192 by 130.13.138.163; Thu, 23 Sep 2004 12:20:58 -0500 Message-ID: From: "Cassie Fontenot" Reply-To: "Cassie Fontenot" To: pilc-admin@ietf.org Subject: Pilc-admin Office XP - $60 Date: Thu, 23 Sep 2004 13:20:58 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--86964299588237955" X-IP: 60.54.215.150 X-Spam-Score: 5.8 (+++++) X-Spam-Flag: YES X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 ----86964299588237955 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable TOP quality software:

Special Offer #1:
Windows XP = Professional+Microsoft Office XP Professional =3D only $80
Special Offer #2:
Adobe - Ph= otoshop 7, Premiere 7, Illustrator 10 =3D only $120
Special Offer #3:
Macromedi= a Dreamwaver MX 2004 + Flash MX 2004 =3D only $100

Also:
Windows 2003 Server
Windows 2000 Workstation
Windows 2000 Server
Windows 2000 Advanced Server
Windows 2000 Datacenter
Windows NT 4.0
Windows Millenium
Windows 98 Second Edition
Windows 95
Office XP Professional
Office 2000
Office 97
MS Plus
MS SQL Server 2000 Enterprise Edition
MS Visual Studio .NET Architect Edition
MS Encarta Encyclopedia Delux 2004
MS Project 2003 Professional
MS Money 2004
MS Streets and Trips 2004
MS Works 7
MS Picture It Premium 9
MS Exchange 2003 Enterprise Server
Adobe Photoshop
Adobe PageMaker
Adobe Illustrator
Adobe Acrobat 6 Professional
Adobe Premiere
Macromedia Dreamwaver MX 2004
Macromedia Flash MX 2004
Macromedia Fireworks MX 2004
Macromedia Freehand MX 11
Corel Draw Graphics Suite 12
Corel Draw Graphics Suite 11
Corel Photo Painter 8
Corel Word Perfect Office 2002
Norton System Works 2003
Borland Delphi 7 Enterprise Edition
Quark Xpress 6 Passport Multilanguage

Enter Here











?2N47A3zVjC9Xk2ysophomore= |pilc-admin@ietf.org">or un*su*bs*cr*ibe =20 ----86964299588237955-- From owner-ietf-provreg@cafax.se Fri Sep 24 14:00:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02273 for ; Fri, 24 Sep 2004 14:00:37 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAuU5-000829-9H for provreg-archive@ietf.org; Fri, 24 Sep 2004 14:07:55 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OHo68v022207 for ; Fri, 24 Sep 2004 19:50:06 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8OHo6Zt001062 for ietf-provreg-outgoing; Fri, 24 Sep 2004 19:50:06 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from central.switch.ch (central.switch.ch [130.59.11.11]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OHo1Vm007081 for ; Fri, 24 Sep 2004 19:50:05 +0200 (MEST) Received: from nmq-245.switch.ch ([130.59.6.245]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1CAuCe-0004iV-00; Fri, 24 Sep 2004 19:49:52 +0200 Date: Fri, 24 Sep 2004 19:48:12 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: enum@ietf.org cc: ietf-provreg@cafax.se Subject: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-00 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Hi! I have just submitted a new I/D: draft-hoeneisen-enum-validation-epp-00 Abstract: This document describes an EPP extension for mapping information about the validation process the ENUM Registrar has applied for the E.164 number (or number range), which the ENUM domain name is based on. Specified in XML, this mapping extends the EPP domain name mapping to provide an additional feature required for the provisioning of E.164 numbers. Until it appears in the archives, you can download it from the following URLs: * http://ietf.hoeneisen.ch/draft-hoeneisen-enum-validation-epp-00.txt * http://ietf.hoeneisen.ch/draft-hoeneisen-enum-validation-epp-00.html I am looking forward to your comments and proposals for improvement. Have fun! cheers, Bernie From owner-ietf-provreg@cafax.se Fri Sep 24 14:32:33 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04155 for ; Fri, 24 Sep 2004 14:32:33 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAuyz-00009D-Ss for provreg-archive@ietf.org; Fri, 24 Sep 2004 14:39:51 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OIQwrn022719 for ; Fri, 24 Sep 2004 20:26:58 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8OIQw65001355 for ietf-provreg-outgoing; Fri, 24 Sep 2004 20:26:58 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OIQrfW018574 for ; Fri, 24 Sep 2004 20:26:54 +0200 (MEST) Received: from vsvapostalgw3.vcorp.ad.vrsn.com (vsvapostalgw3.vcorp.ad.vrsn.com [10.170.12.61]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i8OIOGop022707; Fri, 24 Sep 2004 14:24:16 -0400 (EDT) Received: by vsvapostalgw3.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Fri, 24 Sep 2004 14:26:48 -0400 Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF040D84E6@vsvapostal8.vcorp.ad.vrsn.com> From: "Hollenbeck, Scott" To: "'Bernie Hoeneisen'" , "'enum@ietf.org'" Cc: "'ietf-provreg@cafax.se'" Subject: RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0 Date: Fri, 24 Sep 2004 14:27:09 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f > I am looking forward to your comments and proposals for improvement. It's customary to include an acknowledgements section, especially when much of the text is clearly copied from earlier work done by someone else. I'll review this in more detail when I have more time, but I'm not sure I understand how this can work without also using the ENUM extension [1] I've been working on. Wouldn't an response, for example, also need to return the data described in my draft once the domain exists in the registry? At first glance I think there needs to be some text in your document explaining the relationship to my document. -Scott- [1] http://www.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-05.txt From owner-ietf-provreg@cafax.se Fri Sep 24 14:34:07 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04302 for ; Fri, 24 Sep 2004 14:34:07 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAv0V-0000AM-Iu for provreg-archive@ietf.org; Fri, 24 Sep 2004 14:41:25 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OITLau025788 for ; Fri, 24 Sep 2004 20:29:21 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8OITLfm012742 for ietf-provreg-outgoing; Fri, 24 Sep 2004 20:29:21 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from nic-naa.net (nic-naa.net [216.220.241.233]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OITJDc021153 for ; Fri, 24 Sep 2004 20:29:20 +0200 (MEST) Received: from nic-naa.net (localhost [127.0.0.1]) by nic-naa.net (8.13.1/8.13.1) with ESMTP id i8OESnWL009886; Fri, 24 Sep 2004 14:28:49 GMT (envelope-from brunner@nic-naa.net) Message-Id: <200409241428.i8OESnWL009886@nic-naa.net> To: Bernie Hoeneisen cc: enum@ietf.org, ietf-provreg@cafax.se, brunner@nic-naa.net Subject: Re: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-00 In-Reply-To: Your message of "Fri, 24 Sep 2004 19:48:12 +0200." Date: Fri, 24 Sep 2004 14:28:49 +0000 From: Eric Brunner-Williams in Portland Maine Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.7 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Bernie, I'll read it and try to comment. Eric From owner-ietf-provreg@cafax.se Fri Sep 24 15:38:35 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08885 for ; Fri, 24 Sep 2004 15:38:35 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAw0w-00017C-0P for provreg-archive@ietf.org; Fri, 24 Sep 2004 15:45:54 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OJRInL012346 for ; Fri, 24 Sep 2004 21:27:18 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8OJRIct022097 for ietf-provreg-outgoing; Fri, 24 Sep 2004 21:27:18 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from nic-naa.net (nic-naa.net [216.220.241.233]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OJRC3J006152 for ; Fri, 24 Sep 2004 21:27:12 +0200 (MEST) Received: from nic-naa.net (localhost [127.0.0.1]) by nic-naa.net (8.13.1/8.13.1) with ESMTP id i8OFQfxX010154; Fri, 24 Sep 2004 15:26:41 GMT (envelope-from brunner@nic-naa.net) Message-Id: <200409241526.i8OFQfxX010154@nic-naa.net> To: "Hollenbeck, Scott" cc: "'Bernie Hoeneisen'" , "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" , brunner@nic-naa.net Subject: Re: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0 In-Reply-To: Your message of "Fri, 24 Sep 2004 14:27:09 -0400." <5BEA6CDB196A4241B8BE129D309AA4AF040D84E6@vsvapostal8.vcorp.ad.vrsn.com> Date: Fri, 24 Sep 2004 15:26:41 +0000 From: Eric Brunner-Williams in Portland Maine Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.7 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed > > It's customary to include an acknowledgements section, especially when much > of the text is clearly copied from earlier work done by someone else. > I know how you feel. Leslie just got a variation on my ":43 considered obsolete" to RFC, without a single ack. From owner-ietf-provreg@cafax.se Mon Sep 27 07:42:37 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21616 for ; Mon, 27 Sep 2004 07:42:37 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CBu1T-0003lm-83 for provreg-archive@ietf.org; Mon, 27 Sep 2004 07:50:30 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RBX90i014644 for ; Mon, 27 Sep 2004 13:33:09 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8RBX9rD013337 for ietf-provreg-outgoing; Mon, 27 Sep 2004 13:33:09 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RBX7i0015221 for ; Mon, 27 Sep 2004 13:33:08 +0200 (MEST) Received: from vsvapostalgw3.vcorp.ad.vrsn.com (vsvapostalgw3.vcorp.ad.vrsn.com [10.170.12.61]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i8RBUSop016311; Mon, 27 Sep 2004 07:30:28 -0400 (EDT) Received: by vsvapostalgw3.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Mon, 27 Sep 2004 07:33:03 -0400 Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF040D84F0@vsvapostal8.vcorp.ad.vrsn.com> From: "Hollenbeck, Scott" To: "'Conroy, Lawrence (SMTP)'" Cc: "'Bernie Hoeneisen'" , "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: RE: [Enum] RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-valid ation-epp-0 0 Date: Mon, 27 Sep 2004 07:33:30 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 > There is a reference to the main EPP documents in Bernie's > draft, so I don't > understand the annoyance either. It must be me. A very large portion of the text is copied directly from my documents, with no mention of where it came from. In some contexts this is considered to be plagiarism. The IETF tradition is to recognize building on the work of others by noting contributions in an "Acknowledgements" section. Something like this would be appropriate: "A large portion of the text in this document has been copied from earlier work written by Scott Hollenbeck." There should also be mention of contributions provided by others. I'm all for consistent format and structure of extensions. We shouldn't be passing off text that was written by someone else as new or original thought, though. -Scott- From owner-ietf-provreg@cafax.se Mon Sep 27 08:28:26 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25193 for ; Mon, 27 Sep 2004 08:28:26 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CBujs-0004sg-FS for provreg-archive@ietf.org; Mon, 27 Sep 2004 08:36:20 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RCNGBI026093 for ; Mon, 27 Sep 2004 14:23:16 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8RCNGo2003257 for ietf-provreg-outgoing; Mon, 27 Sep 2004 14:23:16 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from central.switch.ch (central.switch.ch [130.59.11.11]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RCNAXf025762 for ; Mon, 27 Sep 2004 14:23:15 +0200 (MEST) Received: from nmq-245.switch.ch ([130.59.6.245]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1CBuWv-0005fl-00; Mon, 27 Sep 2004 14:22:57 +0200 Date: Mon, 27 Sep 2004 14:20:39 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: "Hollenbeck, Scott" cc: "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0 In-Reply-To: <5BEA6CDB196A4241B8BE129D309AA4AF040D84E6@vsvapostal8.vcorp.ad.vrsn.com> Message-ID: References: <5BEA6CDB196A4241B8BE129D309AA4AF040D84E6@vsvapostal8.vcorp.ad.vrsn.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Hi Scott! On Fri, 24 Sep 2004, Hollenbeck, Scott wrote: > > It's customary to include an acknowledgements section, especially when much > of the text is clearly copied from earlier work done by someone else. > Sorry about my "omission sin"! I will add such an acknowledgements section in the next revision. Yes, I took your draft [1] as a template; because IMHO it has an excellent structure for EPP extensions. This actually also proofs, that I trust your documents! > [...] I'm not sure I understand how this can work without also using the > ENUM extension [1] I've been working on. The both extensions work independently, as they address completely different problems. Your extension [1] is about providing NAPTR records (for the DNS), my proposal [2] about providing validation information, (e.g. to comply legal requirements). > Wouldn't an response, for example, also need to return the > data described in my draft once the domain exists in the registry? Only if the registry supports also your extension [1]. > At first glance I think there needs to be some text in your > document explaining the relationship to my document. As this is not required to understand my validation information proposal [2], it is certainly useful to understand the differences between [1] and [2]. I'll think of something appropriate for the next revision. cheers, Bernie References: [1] http://www.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-05.txt [2] http://ietf.hoeneisen.ch/draft-hoeneisen-enum-validation-epp-00.txt From owner-ietf-provreg@cafax.se Mon Sep 27 15:26:55 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24610 for ; Mon, 27 Sep 2004 15:26:54 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CC1Gu-00045s-1G for provreg-archive@ietf.org; Mon, 27 Sep 2004 15:34:53 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RJAWE2024649 for ; Mon, 27 Sep 2004 21:10:32 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8RJAWSk016492 for ietf-provreg-outgoing; Mon, 27 Sep 2004 21:10:32 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RJAT00005334 for ; Mon, 27 Sep 2004 21:10:29 +0200 (MEST) Received: from vsvapostalgw3.vcorp.ad.vrsn.com (vsvapostalgw3.vcorp.ad.vrsn.com [10.170.12.61]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i8RJ7qop008026; Mon, 27 Sep 2004 15:07:52 -0400 (EDT) Received: by vsvapostalgw3.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Mon, 27 Sep 2004 15:10:27 -0400 Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF040D84FD@vsvapostal8.vcorp.ad.vrsn.com> From: "Hollenbeck, Scott" To: "'Bernie Hoeneisen'" , "'enum@ietf.org'" Cc: "'ietf-provreg@cafax.se'" Subject: RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0 Date: Mon, 27 Sep 2004 15:10:52 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-MIME-Autoconverted: from quoted-printable to 8bit by nic.cafax.se id i8RJAT00013339 Sender: owner-ietf-provreg@cafax.se Precedence: bulk Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by nic.cafax.se id i8RJAWE2024649 X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: quoted-printable OK, I had a chance to take a closer look. I noticed that you're using a 31-character token for the E.164 number. Why is that? An E.164 number c= an contain no more than 15 digits per E.164, so why allow a maximum of 31? = For what it's worth I used a type like this in the EPP contact mapping: With this you get the "+". The country code and the local part are separated by a "." (we did that in provreg mostly for "human eyes" reason= s). The "+" and the "." added to the max E.164 length of 15 digits gives a maximum token length of 17 characters. Also, throughout the document s/M=E4rz/March/ -Scott- From owner-ietf-provreg@cafax.se Tue Sep 28 07:38:27 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14571 for ; Tue, 28 Sep 2004 07:38:26 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCGRE-0007NW-M3 for provreg-archive@ietf.org; Tue, 28 Sep 2004 07:46:33 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SB6k9i023120 for ; Tue, 28 Sep 2004 13:06:46 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8SB6kmT004156 for ietf-provreg-outgoing; Tue, 28 Sep 2004 13:06:46 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SB6eka026073 for ; Tue, 28 Sep 2004 13:06:41 +0200 (MEST) Received: from VSVAPOSTALGW1.vcorp.ad.vrsn.com (vsvapostalgw1.vcorp.ad.vrsn.com [10.170.12.38]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i8SB3wop015707; Tue, 28 Sep 2004 07:04:00 -0400 (EDT) Received: by vsvapostalgw1.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Tue, 28 Sep 2004 07:06:34 -0400 Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF040D850A@vsvapostal8.vcorp.ad.vrsn.com> From: "Hollenbeck, Scott" To: "'Clive D.W. Feather'" Cc: "'Bernie Hoeneisen'" , "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: [ietf-provreg] RE: New I/D: draft-hoeneisen-enum-validation-epp-0 0 Date: Tue, 28 Sep 2004 07:07:03 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 > While I don't see E.164 changing any time soon, there are > cases where local > allocations may be longer than the 15 digit limit, and there > is no harm in > leaving space for expansion. Well, then perhaps a more basic question: why is the number needed in the extension at all? You already have the domain name; the number can be trivially derived from the name. -Scott- From owner-ietf-provreg@cafax.se Tue Sep 28 07:58:57 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15635 for ; Tue, 28 Sep 2004 07:58:56 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCGl3-0007tv-V2 for provreg-archive@ietf.org; Tue, 28 Sep 2004 08:07:03 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SBkxad004796 for ; Tue, 28 Sep 2004 13:46:59 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8SBkx9N023760 for ietf-provreg-outgoing; Tue, 28 Sep 2004 13:46:59 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from central.switch.ch (central.switch.ch [130.59.11.11]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SBkwxK015388 for ; Tue, 28 Sep 2004 13:46:58 +0200 (MEST) Received: from nmq-245.switch.ch ([130.59.6.245]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1CCGRT-0007kV-00; Tue, 28 Sep 2004 13:46:47 +0200 Date: Tue, 28 Sep 2004 13:44:16 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: "Hollenbeck, Scott" cc: "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0 In-Reply-To: <5BEA6CDB196A4241B8BE129D309AA4AF040D84FD@vsvapostal8.vcorp.ad.vrsn.com> Message-ID: References: <5BEA6CDB196A4241B8BE129D309AA4AF040D84FD@vsvapostal8.vcorp.ad.vrsn.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="98048-956900902-1096370539=:3503" Content-ID: Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --98048-956900902-1096370539=:3503 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1; format=flowed Content-ID: Content-Transfer-Encoding: QUOTED-PRINTABLE Hi Scott! Thanks for your feedback! On Mon, 27 Sep 2004, Hollenbeck, Scott wrote: > OK, I had a chance to take a closer look. I noticed that you're using a > 31-character token for the E.164 number. Why is that? An E.164 number c= an > contain no more than 15 digits per E.164, so why allow a maximum of 31? = For > what it's worth I used a type like this in the EPP contact mapping: The idea behind this was to leave it a Registry policy issue (or up to the= =20 validation method documentation), what format to use, in order to keep it= =20 as generic as possible. This would allow over-dialing, and characters=20 such as "-", "(", ")" as seperators. Furthermore one could=20 describe number ranges, e.g. "+41-44-26815xx", with this format. I do not have a strong opinion on which format to use for this. > Also, throughout the document s/M=E4rz/March/ Ouuppps...! This is due to a bug in the "xml2rfc" package. It used my locale settings,= =20 i.e. the environment variable "LC_TIME=3Dde_CH" although any output=20 documents of the xml2rfc tool are in English. I have submitted a Bug=20 Report and informed the Debian maintainer about this issue. I even got=20 immediately a patch! However, this will be correct in the next revision. cheers, Bernie --98048-956900902-1096370539=:3503-- From owner-ietf-provreg@cafax.se Tue Sep 28 08:17:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16760 for ; Tue, 28 Sep 2004 08:17:04 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCH2b-0008Gw-Ll for provreg-archive@ietf.org; Tue, 28 Sep 2004 08:25:11 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SCBMsQ004268 for ; Tue, 28 Sep 2004 14:11:22 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8SCBMl1003357 for ietf-provreg-outgoing; Tue, 28 Sep 2004 14:11:22 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from central.switch.ch (central.switch.ch [130.59.11.11]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SCBHMR008394 for ; Tue, 28 Sep 2004 14:11:21 +0200 (MEST) Received: from nmq-245.switch.ch ([130.59.6.245]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1CCGp2-0000Gz-00; Tue, 28 Sep 2004 14:11:08 +0200 Date: Tue, 28 Sep 2004 14:08:37 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: "Hollenbeck, Scott" cc: "'Clive D.W. Feather'" , "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: [ietf-provreg] RE: New I/D: draft-hoeneisen-enum-validation-epp-0 0 In-Reply-To: <5BEA6CDB196A4241B8BE129D309AA4AF040D850A@vsvapostal8.vcorp.ad.vrsn.com> Message-ID: References: <5BEA6CDB196A4241B8BE129D309AA4AF040D850A@vsvapostal8.vcorp.ad.vrsn.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Hi Scott and Clive! Thanks for your feedback! On Tue, 28 Sep 2004, Hollenbeck, Scott wrote: >> While I don't see E.164 changing any time soon, there are >> cases where local >> allocations may be longer than the 15 digit limit, and there >> is no harm in >> leaving space for expansion. > > Well, then perhaps a more basic question: why is the number needed in the > extension at all? You already have the domain name; the number can be > trivially derived from the name. For the major part of the cases I agree with you. But I am trying to make the extension as generic as possible. Im can imagine, that certain validation procedures might need this optional field. I am even thinking of adding (optional) elements to be used for Contact information of the E.164 number (range) holder, e.g. as reported from the Validation Entity. This could enable easier handling of problem cases at the Registry. cheers, Bernie From owner-ietf-provreg@cafax.se Tue Sep 28 08:21:59 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17299 for ; Tue, 28 Sep 2004 08:21:59 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCH7N-0008Qf-Qz for provreg-archive@ietf.org; Tue, 28 Sep 2004 08:30:06 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SCHchO020806 for ; Tue, 28 Sep 2004 14:17:38 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8SCHcxo010161 for ietf-provreg-outgoing; Tue, 28 Sep 2004 14:17:38 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SCHZds027022 for ; Tue, 28 Sep 2004 14:17:35 +0200 (MEST) Received: from vsvapostalgw3.vcorp.ad.vrsn.com (vsvapostalgw3.vcorp.ad.vrsn.com [10.170.12.61]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i8SCEvop018566; Tue, 28 Sep 2004 08:14:58 -0400 (EDT) Received: by vsvapostalgw3.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Tue, 28 Sep 2004 08:17:33 -0400 Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF040D850B@vsvapostal8.vcorp.ad.vrsn.com> From: "Hollenbeck, Scott" To: "'Bernie Hoeneisen'" Cc: "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: [ietf-provreg] RE: New I/D: draft-hoeneisen-enum-validation-epp-0 0 Date: Tue, 28 Sep 2004 08:18:03 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 > > Well, then perhaps a more basic question: why is the number > needed in the > > extension at all? You already have the domain name; the > number can be > > trivially derived from the name. > > For the major part of the cases I agree with you. > But I am trying to make the extension as generic as possible. > Im can imagine, that certain validation procedures might need this > optional field. I still don't get it. If the number is needed, it can be derived from the domain name. Why carry it twice? The only scenario I can imagine is one in which some kind of formatting or some extra information (such as over-dialing numbers) needs to be preserved. Is that what you have in mind? -Scott- From owner-ietf-provreg@cafax.se Tue Sep 28 09:18:58 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20947 for ; Tue, 28 Sep 2004 09:18:57 -0400 (EDT) Received: from nic.cafax.se ([192.71.228.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCI0W-00019G-7W for provreg-archive@ietf.org; Tue, 28 Sep 2004 09:27:05 -0400 Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SD7RZB029588 for ; Tue, 28 Sep 2004 15:07:27 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8SD7Req007118 for ietf-provreg-outgoing; Tue, 28 Sep 2004 15:07:27 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from central.switch.ch (central.switch.ch [130.59.11.11]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SD7Mfr027473 for ; Tue, 28 Sep 2004 15:07:27 +0200 (MEST) Received: from nmq-245.switch.ch ([130.59.6.245]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1CCHhJ-0004Oy-00; Tue, 28 Sep 2004 15:07:13 +0200 Date: Tue, 28 Sep 2004 15:04:41 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: "Hollenbeck, Scott" cc: "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: [ietf-provreg] RE: New I/D: draft-hoeneisen-enum-validation-epp-0 0 In-Reply-To: <5BEA6CDB196A4241B8BE129D309AA4AF040D850B@vsvapostal8.vcorp.ad.vrsn.com> Message-ID: References: <5BEA6CDB196A4241B8BE129D309AA4AF040D850B@vsvapostal8.vcorp.ad.vrsn.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: owner-ietf-provreg@cafax.se Precedence: bulk X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 On Tue, 28 Sep 2004, Hollenbeck, Scott wrote: >>> Well, then perhaps a more basic question: why is the number >> needed in the >>> extension at all? You already have the domain name; the >> number can be >>> trivially derived from the name. >> >> For the major part of the cases I agree with you. >> But I am trying to make the extension as generic as possible. >> Im can imagine, that certain validation procedures might need this >> optional field. > > I still don't get it. If the number is needed, it can be derived from the > domain name. Why carry it twice? > > The only scenario I can imagine is one in which some kind of formatting or > some extra information (such as over-dialing numbers) needs to be preserved. > Is that what you have in mind? For example. cheers, Bernie From bulletin@computeradmin.org Wed Sep 29 06:52:29 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19297; Wed, 29 Sep 2004 06:52:28 -0400 (EDT) Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CCcCI-00037F-7W; Wed, 29 Sep 2004 07:00:49 -0400 Received: from c-67-165-237-247.client.comcast.net ([67.165.237.247]) by mx2.foretec.com with smtp (Exim 4.24) id 1CCc3h-00075p-N5; Wed, 29 Sep 2004 06:51:42 -0400 Received: from [246.50.4.230] by c-67-165-237-247.client.comcast.net id <2287020-62366>; Wed, 29 Sep 2004 08:56:08 -0300 Message-ID: From: "Admin" To: nemo@ietf.org Subject: ADV: Announcement To All Staff Date: Wed, 29 Sep 04 08:56:08 GMT X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="45EF_7C_40674AFB" X-Spam-Score: 20.6 (++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 00e94c813bef7832af255170dca19e36 This is a multi-part message in MIME format. --45EF_7C_40674AFB Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Attention All Nonprofit Organizations: Members, Staff and Associates: You Must Respond By 5 P.M. Thursday, September 30, 2004. Through a special arrangement, Avtech Direct is offering a limited allotment of BRAND NEW, top of-the-line, name-brand desktop computers at more than 50% off MSRP to all Nonprofit Members and Staff who respond to this message before 5 P.M., Thursday, September 30, 2004. All desktop are brand-new, packed in their original boxes, and come with a full manufacturer's warranty plus a 100% satisfaction guarantee. These professional grade Desktops are fully equipped with 2004 next generation technology, making these the best performing computers money can buy. Avtech Direct is offering these feature rich, top performing Desktop Computers with the latest Intel technology at an amazing price to all who call: 1-800-884-9510 by 5 P.M. Thursday, September 30, 2004 The fast and powerful AT-2400 series Desktop features: * Intel 2.0Ghz Processor for amazing speed and performance * 128MB DDR RAM, --- Upgradeable to 1024 * 20 GB UDMA Hard Drive, --- Upgradeable to 80 GB * 52X CD-Rom Drive, --- Upgradeable to DVD/CDRW * 1.44 Floppy disk drive * Next Generation Technology * ATI Premium video and sound * Full Connectivity with Fax modem/Lan/IEE 1394/USB 2.0 * Soft Touch Keyboard and scroll mouse * Internet Ready * Network Ready * 1 Year parts and labor warranty * Priority customer service and tech support MSRP $699 ........................................ Your Cost $297 How to qualify: 1. You must be a Member, Staff or Associate of a Nonprofit. 2. All desktop computers will be available on a first come first serve basis. 3. You must call 1-800-884-9510 by 5 P.M. Thursday, September 30, 2004 and we will hold the desktops you request on will call. 4. You are not obligated in any way. 5. 100% Satisfaction Guaranteed. Call Avtech Direct 1-800-884-9510 before 5 P.M. Thursday, September 30, 20= 04 Visit our website at http://www.avtechdirectcomputers.com If you wish to unsubscribe from this list, please go to: http://www.computeradvice.org/unsubscribe.asp Avtech Direct 22647 Ventura Blvd., Suite 374 Woodland Hills, CA 91364 --45EF_7C_40674AFB-- Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SD7RZB029588 for ; Tue, 28 Sep 2004 15:07:27 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8SD7Req007118 for ietf-provreg-outgoing; Tue, 28 Sep 2004 15:07:27 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from central.switch.ch (central.switch.ch [130.59.11.11]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SD7Mfr027473 for ; Tue, 28 Sep 2004 15:07:27 +0200 (MEST) Received: from nmq-245.switch.ch ([130.59.6.245]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1CCHhJ-0004Oy-00; Tue, 28 Sep 2004 15:07:13 +0200 Date: Tue, 28 Sep 2004 15:04:41 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: "Hollenbeck, Scott" cc: "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: [ietf-provreg] RE: New I/D: draft-hoeneisen-enum-validation-epp-0 0 In-Reply-To: <5BEA6CDB196A4241B8BE129D309AA4AF040D850B@vsvapostal8.vcorp.ad.vrsn.com> Message-ID: References: <5BEA6CDB196A4241B8BE129D309AA4AF040D850B@vsvapostal8.vcorp.ad.vrsn.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: owner-ietf-provreg@cafax.se Precedence: bulk On Tue, 28 Sep 2004, Hollenbeck, Scott wrote: >>> Well, then perhaps a more basic question: why is the number >> needed in the >>> extension at all? You already have the domain name; the >> number can be >>> trivially derived from the name. >> >> For the major part of the cases I agree with you. >> But I am trying to make the extension as generic as possible. >> Im can imagine, that certain validation procedures might need this >> optional field. > > I still don't get it. If the number is needed, it can be derived from the > domain name. Why carry it twice? > > The only scenario I can imagine is one in which some kind of formatting or > some extra information (such as over-dialing numbers) needs to be preserved. > Is that what you have in mind? For example. cheers, Bernie Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SCHchO020806 for ; Tue, 28 Sep 2004 14:17:38 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8SCHcxo010161 for ietf-provreg-outgoing; Tue, 28 Sep 2004 14:17:38 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SCHZds027022 for ; Tue, 28 Sep 2004 14:17:35 +0200 (MEST) Received: from vsvapostalgw3.vcorp.ad.vrsn.com (vsvapostalgw3.vcorp.ad.vrsn.com [10.170.12.61]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i8SCEvop018566; Tue, 28 Sep 2004 08:14:58 -0400 (EDT) Received: by vsvapostalgw3.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Tue, 28 Sep 2004 08:17:33 -0400 Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF040D850B@vsvapostal8.vcorp.ad.vrsn.com> From: "Hollenbeck, Scott" To: "'Bernie Hoeneisen'" Cc: "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: [ietf-provreg] RE: New I/D: draft-hoeneisen-enum-validation-epp-0 0 Date: Tue, 28 Sep 2004 08:18:03 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Sender: owner-ietf-provreg@cafax.se Precedence: bulk > > Well, then perhaps a more basic question: why is the number > needed in the > > extension at all? You already have the domain name; the > number can be > > trivially derived from the name. > > For the major part of the cases I agree with you. > But I am trying to make the extension as generic as possible. > Im can imagine, that certain validation procedures might need this > optional field. I still don't get it. If the number is needed, it can be derived from the domain name. Why carry it twice? The only scenario I can imagine is one in which some kind of formatting or some extra information (such as over-dialing numbers) needs to be preserved. Is that what you have in mind? -Scott- Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SCBMsQ004268 for ; Tue, 28 Sep 2004 14:11:22 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8SCBMl1003357 for ietf-provreg-outgoing; Tue, 28 Sep 2004 14:11:22 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from central.switch.ch (central.switch.ch [130.59.11.11]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SCBHMR008394 for ; Tue, 28 Sep 2004 14:11:21 +0200 (MEST) Received: from nmq-245.switch.ch ([130.59.6.245]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1CCGp2-0000Gz-00; Tue, 28 Sep 2004 14:11:08 +0200 Date: Tue, 28 Sep 2004 14:08:37 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: "Hollenbeck, Scott" cc: "'Clive D.W. Feather'" , "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: [ietf-provreg] RE: New I/D: draft-hoeneisen-enum-validation-epp-0 0 In-Reply-To: <5BEA6CDB196A4241B8BE129D309AA4AF040D850A@vsvapostal8.vcorp.ad.vrsn.com> Message-ID: References: <5BEA6CDB196A4241B8BE129D309AA4AF040D850A@vsvapostal8.vcorp.ad.vrsn.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: owner-ietf-provreg@cafax.se Precedence: bulk Hi Scott and Clive! Thanks for your feedback! On Tue, 28 Sep 2004, Hollenbeck, Scott wrote: >> While I don't see E.164 changing any time soon, there are >> cases where local >> allocations may be longer than the 15 digit limit, and there >> is no harm in >> leaving space for expansion. > > Well, then perhaps a more basic question: why is the number needed in the > extension at all? You already have the domain name; the number can be > trivially derived from the name. For the major part of the cases I agree with you. But I am trying to make the extension as generic as possible. Im can imagine, that certain validation procedures might need this optional field. I am even thinking of adding (optional) elements to be used for Contact information of the E.164 number (range) holder, e.g. as reported from the Validation Entity. This could enable easier handling of problem cases at the Registry. cheers, Bernie Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SBkxad004796 for ; Tue, 28 Sep 2004 13:46:59 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8SBkx9N023760 for ietf-provreg-outgoing; Tue, 28 Sep 2004 13:46:59 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from central.switch.ch (central.switch.ch [130.59.11.11]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SBkwxK015388 for ; Tue, 28 Sep 2004 13:46:58 +0200 (MEST) Received: from nmq-245.switch.ch ([130.59.6.245]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1CCGRT-0007kV-00; Tue, 28 Sep 2004 13:46:47 +0200 Date: Tue, 28 Sep 2004 13:44:16 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: "Hollenbeck, Scott" cc: "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0 In-Reply-To: <5BEA6CDB196A4241B8BE129D309AA4AF040D84FD@vsvapostal8.vcorp.ad.vrsn.com> Message-ID: References: <5BEA6CDB196A4241B8BE129D309AA4AF040D84FD@vsvapostal8.vcorp.ad.vrsn.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="98048-956900902-1096370539=:3503" Content-ID: Sender: owner-ietf-provreg@cafax.se Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --98048-956900902-1096370539=:3503 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: Hi Scott! Thanks for your feedback! On Mon, 27 Sep 2004, Hollenbeck, Scott wrote: > OK, I had a chance to take a closer look. I noticed that you're using a > 31-character token for the E.164 number. Why is that? An E.164 number c= an > contain no more than 15 digits per E.164, so why allow a maximum of 31? = For > what it's worth I used a type like this in the EPP contact mapping: The idea behind this was to leave it a Registry policy issue (or up to the= =20 validation method documentation), what format to use, in order to keep it= =20 as generic as possible. This would allow over-dialing, and characters=20 such as "-", "(", ")" as seperators. Furthermore one could=20 describe number ranges, e.g. "+41-44-26815xx", with this format. I do not have a strong opinion on which format to use for this. > Also, throughout the document s/M=E4rz/March/ Ouuppps...! This is due to a bug in the "xml2rfc" package. It used my locale settings,= =20 i.e. the environment variable "LC_TIME=3Dde_CH" although any output=20 documents of the xml2rfc tool are in English. I have submitted a Bug=20 Report and informed the Debian maintainer about this issue. I even got=20 immediately a patch! However, this will be correct in the next revision. cheers, Bernie --98048-956900902-1096370539=:3503-- Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SB6k9i023120 for ; Tue, 28 Sep 2004 13:06:46 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8SB6kmT004156 for ietf-provreg-outgoing; Tue, 28 Sep 2004 13:06:46 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8SB6eka026073 for ; Tue, 28 Sep 2004 13:06:41 +0200 (MEST) Received: from VSVAPOSTALGW1.vcorp.ad.vrsn.com (vsvapostalgw1.vcorp.ad.vrsn.com [10.170.12.38]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i8SB3wop015707; Tue, 28 Sep 2004 07:04:00 -0400 (EDT) Received: by vsvapostalgw1.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Tue, 28 Sep 2004 07:06:34 -0400 Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF040D850A@vsvapostal8.vcorp.ad.vrsn.com> From: "Hollenbeck, Scott" To: "'Clive D.W. Feather'" Cc: "'Bernie Hoeneisen'" , "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: [ietf-provreg] RE: New I/D: draft-hoeneisen-enum-validation-epp-0 0 Date: Tue, 28 Sep 2004 07:07:03 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Sender: owner-ietf-provreg@cafax.se Precedence: bulk > While I don't see E.164 changing any time soon, there are > cases where local > allocations may be longer than the 15 digit limit, and there > is no harm in > leaving space for expansion. Well, then perhaps a more basic question: why is the number needed in the extension at all? You already have the domain name; the number can be trivially derived from the name. -Scott- Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RJAWE2024649 for ; Mon, 27 Sep 2004 21:10:32 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8RJAWSk016492 for ietf-provreg-outgoing; Mon, 27 Sep 2004 21:10:32 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RJAT00005334 for ; Mon, 27 Sep 2004 21:10:29 +0200 (MEST) Received: from vsvapostalgw3.vcorp.ad.vrsn.com (vsvapostalgw3.vcorp.ad.vrsn.com [10.170.12.61]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i8RJ7qop008026; Mon, 27 Sep 2004 15:07:52 -0400 (EDT) Received: by vsvapostalgw3.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Mon, 27 Sep 2004 15:10:27 -0400 Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF040D84FD@vsvapostal8.vcorp.ad.vrsn.com> From: "Hollenbeck, Scott" To: "'Bernie Hoeneisen'" , "'enum@ietf.org'" Cc: "'ietf-provreg@cafax.se'" Subject: RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0 Date: Mon, 27 Sep 2004 15:10:52 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nic.cafax.se id i8RJAT00013339 Sender: owner-ietf-provreg@cafax.se Precedence: bulk OK, I had a chance to take a closer look. I noticed that you're using a 31-character token for the E.164 number. Why is that? An E.164 number can contain no more than 15 digits per E.164, so why allow a maximum of 31? For what it's worth I used a type like this in the EPP contact mapping: With this you get the "+". The country code and the local part are separated by a "." (we did that in provreg mostly for "human eyes" reasons). The "+" and the "." added to the max E.164 length of 15 digits gives a maximum token length of 17 characters. Also, throughout the document s/März/March/ -Scott- Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RCNGBI026093 for ; Mon, 27 Sep 2004 14:23:16 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8RCNGo2003257 for ietf-provreg-outgoing; Mon, 27 Sep 2004 14:23:16 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from central.switch.ch (central.switch.ch [130.59.11.11]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RCNAXf025762 for ; Mon, 27 Sep 2004 14:23:15 +0200 (MEST) Received: from nmq-245.switch.ch ([130.59.6.245]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1CBuWv-0005fl-00; Mon, 27 Sep 2004 14:22:57 +0200 Date: Mon, 27 Sep 2004 14:20:39 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: "Hollenbeck, Scott" cc: "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0 In-Reply-To: <5BEA6CDB196A4241B8BE129D309AA4AF040D84E6@vsvapostal8.vcorp.ad.vrsn.com> Message-ID: References: <5BEA6CDB196A4241B8BE129D309AA4AF040D84E6@vsvapostal8.vcorp.ad.vrsn.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: owner-ietf-provreg@cafax.se Precedence: bulk Hi Scott! On Fri, 24 Sep 2004, Hollenbeck, Scott wrote: > > It's customary to include an acknowledgements section, especially when much > of the text is clearly copied from earlier work done by someone else. > Sorry about my "omission sin"! I will add such an acknowledgements section in the next revision. Yes, I took your draft [1] as a template; because IMHO it has an excellent structure for EPP extensions. This actually also proofs, that I trust your documents! > [...] I'm not sure I understand how this can work without also using the > ENUM extension [1] I've been working on. The both extensions work independently, as they address completely different problems. Your extension [1] is about providing NAPTR records (for the DNS), my proposal [2] about providing validation information, (e.g. to comply legal requirements). > Wouldn't an response, for example, also need to return the > data described in my draft once the domain exists in the registry? Only if the registry supports also your extension [1]. > At first glance I think there needs to be some text in your > document explaining the relationship to my document. As this is not required to understand my validation information proposal [2], it is certainly useful to understand the differences between [1] and [2]. I'll think of something appropriate for the next revision. cheers, Bernie References: [1] http://www.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-05.txt [2] http://ietf.hoeneisen.ch/draft-hoeneisen-enum-validation-epp-00.txt Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RBX90i014644 for ; Mon, 27 Sep 2004 13:33:09 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8RBX9rD013337 for ietf-provreg-outgoing; Mon, 27 Sep 2004 13:33:09 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8RBX7i0015221 for ; Mon, 27 Sep 2004 13:33:08 +0200 (MEST) Received: from vsvapostalgw3.vcorp.ad.vrsn.com (vsvapostalgw3.vcorp.ad.vrsn.com [10.170.12.61]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i8RBUSop016311; Mon, 27 Sep 2004 07:30:28 -0400 (EDT) Received: by vsvapostalgw3.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Mon, 27 Sep 2004 07:33:03 -0400 Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF040D84F0@vsvapostal8.vcorp.ad.vrsn.com> From: "Hollenbeck, Scott" To: "'Conroy, Lawrence (SMTP)'" Cc: "'Bernie Hoeneisen'" , "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" Subject: RE: [Enum] RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-valid ation-epp-0 0 Date: Mon, 27 Sep 2004 07:33:30 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Sender: owner-ietf-provreg@cafax.se Precedence: bulk > There is a reference to the main EPP documents in Bernie's > draft, so I don't > understand the annoyance either. It must be me. A very large portion of the text is copied directly from my documents, with no mention of where it came from. In some contexts this is considered to be plagiarism. The IETF tradition is to recognize building on the work of others by noting contributions in an "Acknowledgements" section. Something like this would be appropriate: "A large portion of the text in this document has been copied from earlier work written by Scott Hollenbeck." There should also be mention of contributions provided by others. I'm all for consistent format and structure of extensions. We shouldn't be passing off text that was written by someone else as new or original thought, though. -Scott- Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OJRInL012346 for ; Fri, 24 Sep 2004 21:27:18 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8OJRIct022097 for ietf-provreg-outgoing; Fri, 24 Sep 2004 21:27:18 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from nic-naa.net (nic-naa.net [216.220.241.233]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OJRC3J006152 for ; Fri, 24 Sep 2004 21:27:12 +0200 (MEST) Received: from nic-naa.net (localhost [127.0.0.1]) by nic-naa.net (8.13.1/8.13.1) with ESMTP id i8OFQfxX010154; Fri, 24 Sep 2004 15:26:41 GMT (envelope-from brunner@nic-naa.net) Message-Id: <200409241526.i8OFQfxX010154@nic-naa.net> To: "Hollenbeck, Scott" cc: "'Bernie Hoeneisen'" , "'enum@ietf.org'" , "'ietf-provreg@cafax.se'" , brunner@nic-naa.net Subject: Re: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0 In-Reply-To: Your message of "Fri, 24 Sep 2004 14:27:09 -0400." <5BEA6CDB196A4241B8BE129D309AA4AF040D84E6@vsvapostal8.vcorp.ad.vrsn.com> Date: Fri, 24 Sep 2004 15:26:41 +0000 From: Eric Brunner-Williams in Portland Maine Sender: owner-ietf-provreg@cafax.se Precedence: bulk > > It's customary to include an acknowledgements section, especially when much > of the text is clearly copied from earlier work done by someone else. > I know how you feel. Leslie just got a variation on my ":43 considered obsolete" to RFC, without a single ack. Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OITLau025788 for ; Fri, 24 Sep 2004 20:29:21 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8OITLfm012742 for ietf-provreg-outgoing; Fri, 24 Sep 2004 20:29:21 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from nic-naa.net (nic-naa.net [216.220.241.233]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OITJDc021153 for ; Fri, 24 Sep 2004 20:29:20 +0200 (MEST) Received: from nic-naa.net (localhost [127.0.0.1]) by nic-naa.net (8.13.1/8.13.1) with ESMTP id i8OESnWL009886; Fri, 24 Sep 2004 14:28:49 GMT (envelope-from brunner@nic-naa.net) Message-Id: <200409241428.i8OESnWL009886@nic-naa.net> To: Bernie Hoeneisen cc: enum@ietf.org, ietf-provreg@cafax.se, brunner@nic-naa.net Subject: Re: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-00 In-Reply-To: Your message of "Fri, 24 Sep 2004 19:48:12 +0200." Date: Fri, 24 Sep 2004 14:28:49 +0000 From: Eric Brunner-Williams in Portland Maine Sender: owner-ietf-provreg@cafax.se Precedence: bulk Bernie, I'll read it and try to comment. Eric Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OIQwrn022719 for ; Fri, 24 Sep 2004 20:26:58 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8OIQw65001355 for ietf-provreg-outgoing; Fri, 24 Sep 2004 20:26:58 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OIQrfW018574 for ; Fri, 24 Sep 2004 20:26:54 +0200 (MEST) Received: from vsvapostalgw3.vcorp.ad.vrsn.com (vsvapostalgw3.vcorp.ad.vrsn.com [10.170.12.61]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i8OIOGop022707; Fri, 24 Sep 2004 14:24:16 -0400 (EDT) Received: by vsvapostalgw3.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Fri, 24 Sep 2004 14:26:48 -0400 Message-ID: <5BEA6CDB196A4241B8BE129D309AA4AF040D84E6@vsvapostal8.vcorp.ad.vrsn.com> From: "Hollenbeck, Scott" To: "'Bernie Hoeneisen'" , "'enum@ietf.org'" Cc: "'ietf-provreg@cafax.se'" Subject: RE: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-0 0 Date: Fri, 24 Sep 2004 14:27:09 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Sender: owner-ietf-provreg@cafax.se Precedence: bulk > I am looking forward to your comments and proposals for improvement. It's customary to include an acknowledgements section, especially when much of the text is clearly copied from earlier work done by someone else. I'll review this in more detail when I have more time, but I'm not sure I understand how this can work without also using the ENUM extension [1] I've been working on. Wouldn't an response, for example, also need to return the data described in my draft once the domain exists in the registry? At first glance I think there needs to be some text in your document explaining the relationship to my document. -Scott- [1] http://www.ietf.org/internet-drafts/draft-ietf-enum-epp-e164-05.txt Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OHo68v022207 for ; Fri, 24 Sep 2004 19:50:06 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i8OHo6Zt001062 for ietf-provreg-outgoing; Fri, 24 Sep 2004 19:50:06 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from central.switch.ch (central.switch.ch [130.59.11.11]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i8OHo1Vm007081 for ; Fri, 24 Sep 2004 19:50:05 +0200 (MEST) Received: from nmq-245.switch.ch ([130.59.6.245]) by central.switch.ch with esmtp (Exim 3.20 #1) id 1CAuCe-0004iV-00; Fri, 24 Sep 2004 19:49:52 +0200 Date: Fri, 24 Sep 2004 19:48:12 +0200 (CEST) From: Bernie Hoeneisen X-X-Sender: bhoeneis@machb To: enum@ietf.org cc: ietf-provreg@cafax.se Subject: [ietf-provreg] New I/D: draft-hoeneisen-enum-validation-epp-00 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: owner-ietf-provreg@cafax.se Precedence: bulk Hi! I have just submitted a new I/D: draft-hoeneisen-enum-validation-epp-00 Abstract: This document describes an EPP extension for mapping information about the validation process the ENUM Registrar has applied for the E.164 number (or number range), which the ENUM domain name is based on. Specified in XML, this mapping extends the EPP domain name mapping to provide an additional feature required for the provisioning of E.164 numbers. Until it appears in the archives, you can download it from the following URLs: * http://ietf.hoeneisen.ch/draft-hoeneisen-enum-validation-epp-00.txt * http://ietf.hoeneisen.ch/draft-hoeneisen-enum-validation-epp-00.html I am looking forward to your comments and proposals for improvement. Have fun! cheers, Bernie Return-Path: Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i88GujDT001714 for ; Wed, 8 Sep 2004 18:56:45 +0200 (MEST) Received: (from majordom@localhost) by nic.cafax.se (8.12.11/8.12.11/Submit) id i88GujO8020413 for ietf-provreg-outgoing; Wed, 8 Sep 2004 18:56:45 +0200 (MEST) X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f Received: from falcon.verisign.com (falcon.verisign.com [216.168.239.71]) by nic.cafax.se (8.12.11/8.12.11) with ESMTP id i88Gui34008764 for ; Wed, 8 Sep 2004 18:56:44 +0200 (MEST) Received: from vsvapostalgw3.vcorp.ad.vrsn.com (vsvapostalgw3.vcorp.ad.vrsn.com [10.170.12.61]) by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id i88GsRop017674 for ; Wed, 8 Sep 2004 12:54:27 -0400 (EDT) Received: by vsvapostalgw3.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72) id ; Wed, 8 Sep 2004 12:56:38 -0400 Message-ID: <07241BB00D6943429D073403834717CE027E3B@dul1wnexm04.vcorp.ad.vrsn.com> From: "Gould, James" To: "'ietf-provreg@cafax.se'" Subject: [ietf-provreg] Support for multiple status values in the Domain Registry Grace P eriod Mapping Date: Wed, 8 Sep 2004 12:56:38 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C495C4.CE718010" Sender: owner-ietf-provreg@cafax.se Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C495C4.CE718010 Content-Type: text/plain All, Currently the Domain Registry Grace Period Mapping only supports specifying a single rgp:statusType in the respDataType. I believe should be changed to . The issue is that a domain might be in multiple grace periods and therefore returning multiple grace period statuses should be allowed. For example, a Domain can be created and renewed one day later, which means that the domain is in the addPeriod and the renewPeriod. Does anyone have a similar issue or have an issue with supporting multiple RGP statuses? JG James F. Gould VeriSign Naming and Directory Services jgould@verisign.com This message is intended for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized use, distribution, or disclosure is strictly prohibited. If you have received this message in error, please notify sender immediately and destroy/delete the original transmission ------_=_NextPart_001_01C495C4.CE718010 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

All,

 

Currently the =
Domain Registry Grace Period Mapping only supports =
specifying a single rgp:statusType in the respDataType.  I believe =
<element name=3D"rgpStatus" =
type=3D"rgp:statusType"/> should be changed to <element =
name=3D"rgpStatus" type=3D"rgp:statusType" =
maxOccurs=3D"7 or unbounded"/>.  The =
issue is that a domain might be in multiple grace periods and therefore =
returning multiple grace period statuses should be allowed.  For =
example, a Domain can be created and renewed one day later, which means =
that the domain is in the addPeriod and the renewPeriod.  =

 

Does anyone have a similar issue or have an issue = with supporting multiple RGP statuses? 

 

 

JG

 

James F. Gould

VeriSign = Naming and Directory Services

jgould@verisign.com

 

 

This message is intended for the use of the individual or = entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any = unauthorized use, distribution, or disclosure is strictly prohibited. If you have = received this message in error, please notify sender immediately and = destroy/delete the original transmission

 

------_=_NextPart_001_01C495C4.CE718010--