From tmwqjmzdanb@shasta.com Fri Oct 1 00:08: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 AAA02852; Fri, 1 Oct 2004 00:08:38 -0400 (EDT) Received: from p1009-ipbf11fukuokachu.fukuoka.ocn.ne.jp ([221.184.210.9]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CDErA-0003tx-A1; Fri, 01 Oct 2004 00:17:21 -0400 Received: from 4.105.208.228 by 221.184.210.9; Fri, 01 Oct 2004 09:00:32 +0400 Message-ID: From: "Lorenzo Dawson" Reply-To: "Lorenzo Dawson" To: dhcwg-web-archive@ietf.org Subject: legal software at half the price Date: Fri, 01 Oct 2004 00:00:32 -0500 X-Mailer: AOL 9.0 for Windows US sub 783 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--938097625815456" X-Priority: 5 X-MSMail-Priority: Low X-IP: 16.232.208.160 X-Spam-Score: 18.0 (++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 ----938097625815456 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable











herodotus symphonybrow gymnast poboxfaculty lineal flakyarabia sonority embanklipid mexican spoofpalestinian stellar celebesspringe womanhood absenteepredicate orpheus noabide aggressor trompeprovision compellable duplicablemurray onyx diophantinedivan doughnut assumefreedman cutover combapropos elisabeth matriculatedixie doppler knickerbockerimp eden beautifullazybones interpolant tricksterdysentery alcoa apologycompulsion dormitory shoddysawyer woeful insufferablethrash trustworthy ksahmadabad lesbian springecelebrate juvenile medicisept antiquated slavonicbone castigate dismissalhefty stratospheric arduouscontraband hereinabove sylvaniabolshoi megavolt chinesebloodshed neither virginiaaphid exudate airfarebotanic clarence bandmelancholy elastic asphaltmetallurgic cook digitregatta seize malcontentkinky committable clarifywritten brevet autismretina vote thyminecuisine create legacywholesome =20 ----938097625815456-- From skmiziqtc@tintin.org Fri Oct 1 08:58: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 IAA26060; Fri, 1 Oct 2004 08:58:58 -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 1CDN8I-0006ev-UW; Fri, 01 Oct 2004 09:07:46 -0400 Received: from [221.139.246.175] (helo=MAHOME) by mx2.foretec.com with smtp (Exim 4.24) id 1CDMzm-0002kJ-6s; Fri, 01 Oct 2004 08:58:46 -0400 Received: from 167.56.14.162 by 221.139.246.175; Fri, 01 Oct 2004 15:53:26 +0300 Message-ID: From: "Omar Askew" Reply-To: "Omar Askew" To: dccp-admin@ietf.org, dccp-request@ietf.org, dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org Subject: Virus Alert - september 28th Date: Fri, 01 Oct 2004 08:50:26 -0400 X-Mailer: AOL 8.0 for Windows US sub 960 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--984103748671027" X-Priority: 5 X-MSMail-Priority: Low X-IP: 166.24.148.38 X-Spam-Score: 15.6 (+++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 52e1467c2184c31006318542db5614d5 ----984103748671027 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove




purposeful suburbelectrocardiograph session chumarc glove alignsomers debugger skiddycampanile docket snakeectopic lundberg aerospacealto implacable aubreybale ago railroadtailwind corrigible bellinikleenex demystify manometerbreath construct eliminategoat guyana fareupsetting luminescent documentvixen booze exacerbatepocono cairo agingpakistan towboat groutapplied mettle dowrycommitted krieger nowhereamalgam assist avertivebackpack muir polonaisecorbett deign balmyhippo percussion erskinepaucity benefactor ineffablemuff croatia fissilecomposure longleg mittquinn moiseyev iodinateflatware brain procrusteangyro stubborn lawdanube babysit frankfurtercursive barnhard benzeneshea savage chancerybill foxglove chopinselenite rudyard uscrefusal breathe vampratiocinate parochial enquiryerlenmeyer chambers waxworkcolt eulerian apiecererouting skunk byalmanac ----984103748671027-- From dhcwg-bounces@ietf.org Fri Oct 1 14:36:25 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 OAA05308 for ; Fri, 1 Oct 2004 14:36:25 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDSP6-000750-EU for dhcwg-web-archive@ietf.org; Fri, 01 Oct 2004 14:45:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDRt7-0007Xh-5F; Fri, 01 Oct 2004 14:12:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDRTp-0003sK-43 for dhcwg@megatron.ietf.org; Fri, 01 Oct 2004 13:46:05 -0400 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 NAA00229 for ; Fri, 1 Oct 2004 13:46:02 -0400 (EDT) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDRcJ-0005Pd-QU for dhcwg@ietf.org; Fri, 01 Oct 2004 13:54:52 -0400 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 01 Oct 2004 14:03:22 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i91HjUr5024284; Fri, 1 Oct 2004 13:45:31 -0400 (EDT) Received: from volzw2k (che-vpn-cluster-2-174.cisco.com [10.86.242.174]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ALZ27455; Fri, 1 Oct 2004 13:45:27 -0400 (EDT) From: "Bernie Volz" To: "'Soohong Daniel Park'" , "'Ralph Droms'" , Subject: RE: [dhcwg] IPv6 tunnelling options for IPv4 Date: Fri, 1 Oct 2004 13:45:27 -0400 Organization: Cisco Message-ID: <002201c4a7de$708773c0$6501a8c0@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4939.300 Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 Content-Transfer-Encoding: quoted-printable X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f Content-Transfer-Encoding: quoted-printable Hi: Because there are so many different tunnel technologies and so many different ways in which these can be used, clarity would be extremely useful. So, I'd highly recommend adding diagrams and descriptions of the likely uses unless there are good IETF documents elsewhere that can be referenced (and referenced explicitly, with figure and section numbers). I don't understand the diagram you included Daniel. Modifying Ralph's, perhaps it should look like: IPv6|<-------------IPv4 only----------->|<--IPv6--... +-------+ IPv4 +--------+ | Dual | network | Tunnel | | Host +------------core----------+endpoint| +-------+ | +--------+ +---+--+ | DHCP | |server| +------+ The Dual [Stack] host tunnels traffic over IPv4 to get IPv6 = connectivity. I'm also wondering whether there would ever need to be any redundancy in = the tunnel end-points and whether returning a list of IPv4 addresses would = be appropriate. The node can try the first, if no response (not exactly = sure how it would tell - no RA?), it can try the others? But perhaps this is unneeded complexity at this time as there may not be any easy way for a = node to tell if the end-point is up? - Bernie > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20 > On Behalf Of Soohong Daniel Park > Sent: Thursday, September 30, 2004 8:09 PM > To: Ralph Droms; dhcwg@ietf.org > Subject: RE: [dhcwg] IPv6 tunnelling options for IPv4 >=20 >=20 > > I've been reviewing draft-daniel-dhc-ipv6in4-opt-04.txt - does=20 > > draft-daniel-dhc-ipv6in4-opt-04.txt specify "configured=20 > IPv6-over-IPv4=20 > > tunneling", as described in section 4 of RFC 2893? If so,=20 > it would be=20 > > helpful to include a specific reference, as there are numerous=20 > > tunneling and "IPv6-xxx-IPv4" transition mechanisms... >=20 > So, I've added this concern into the revised version. >=20 > >=20 > > I can imagine the mechanism in > > draft-daniel-dhc-ipv6in4-opt-04.txt as being > > useful in the following scenario: > >=20 > > <---IPv6---->|<-------------IPv4 only----------->|<--IPv6--... > >=20 > > +-------+ +------+ +--------+ > > | CPE | | Edge | ISP | Tunnel | > > |gateway+-----+Router+-----core-----+endpoint| > > +-------+ +------+ | +--------+ > > +---+--+ > > | DHCP | > > |server| > > +------+ > >=20 > > In this scenario, the CPE gateway uses DHCPv4 to obtain its IPv4 > > address and > > other configuration information. The DHCPv4 configured=20 > tunnel endpoint > > option would provide the IPv4 address of the ISP tunnel endpoint=20 > > as part of > > the DHCPv4 configuration process to the CPE gateway, which=20 > would then use > > that IPv4 address as the destination to tunnel IPv6 traffic from the > > customer network through the IPv4-only portion of the ISP network. > >=20 >=20 > Also, this option is useful for dual stack user to obtain its=20 > IPv6 connectivity > via IPv6-over-IPv4 tunnel within its IPv4 network. >=20 > [DHCP server] > | > | > <-----IPv4--------------------+------------------------>IPv6 > [IPv4/6 user]=3D=3DIPv6-over-IPv4 Tunnel=3D=3D=3D> >=20 >=20 > > If I have this scenario right, it would help to include a=20 > > description of it > > in draft-daniel-dhc-ipv6in4-opt-04.txt, both to clarify the=20 > use of the > > option and motivate the requirements for its definition. > =20 > Originally, I thought of this point as out of scope of the=20 > draft because > several similar draft were proposed in this WG without specific=20 > description of use case like mine. If needed, it can be done simply. >=20 > > Is the expectation in draft-daniel-dhc-ipv6in4-opt-04.txt=20 > that the tunnel, > > once established, looks like a simple link to the IPv6 stack? =20 > > That is, will > > RAs be exchanged and ND be run across the link? Will the=20 > tunnel endpoints > > use a routing protocol? >=20 > It was also tested and added into the new version. RA runs well=20 > via this configured tunnel. >=20 >=20 >=20 > Daniel (Soohong Daniel Park) > Mobile Platform Lab. Samsung Electronics. >=20 > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg >=20 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Oct 1 20:11: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 UAA12145 for ; Fri, 1 Oct 2004 20:11:04 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDXd0-0001Sk-4W for dhcwg-web-archive@ietf.org; Fri, 01 Oct 2004 20:19:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDXBF-0006gZ-A7; Fri, 01 Oct 2004 19:51:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDX3G-00006T-Rr for dhcwg@megatron.ietf.org; Fri, 01 Oct 2004 19:43:02 -0400 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 TAA10585 for ; Fri, 1 Oct 2004 19:42:59 -0400 (EDT) Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDXBd-0000i0-Oe for dhcwg@ietf.org; Fri, 01 Oct 2004 19:51:52 -0400 Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) id <0I4X00E0LJ6IIE@mailout1.samsung.com> for dhcwg@ietf.org; Sat, 02 Oct 2004 08:42:18 +0900 (KST) Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0I4X0056QJ64VV@mailout1.samsung.com> for dhcwg@ietf.org; Sat, 02 Oct 2004 08:42:04 +0900 (KST) Received: from LocalHost ([168.219.198.109]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0I4X004WAJ64KA@mmp2.samsung.com> for dhcwg@ietf.org; Sat, 02 Oct 2004 08:42:04 +0900 (KST) Date: Sat, 02 Oct 2004 08:43:25 +0900 From: Soohong Daniel Park Subject: RE: [dhcwg] IPv6 tunnelling options for IPv4 In-reply-to: <002201c4a7de$708773c0$6501a8c0@amer.cisco.com> To: Bernie Volz , "'Ralph Droms'" , dhcwg@ietf.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Content-Transfer-Encoding: 7BIT X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Content-Transfer-Encoding: 7BIT Hi Bernie > Because there are so many different tunnel technologies and so many > different ways in which these can be used, clarity would be extremely > useful. So, I'd highly recommend adding diagrams and descriptions of the > likely uses unless there are good IETF documents elsewhere that can be > referenced (and referenced explicitly, with figure and section numbers). no problem here. > I don't understand the diagram you included Daniel. Modifying Ralph's, > perhaps it should look like: > > IPv6|<-------------IPv4 only----------->|<--IPv6--... > > +-------+ IPv4 +--------+ > | Dual | network | Tunnel | > | Host +------------core----------+endpoint| > +-------+ | +--------+ > +---+--+ > | DHCP | > |server| > +------+ > > The Dual [Stack] host tunnels traffic over IPv4 to get IPv6 connectivity. It's why we need a IPv6-over-IPv4 tunnel. There are several possible use cases according to this tunnel and your depict is one of them. > I'm also wondering whether there would ever need to be any > redundancy in the > tunnel end-points and whether returning a list of IPv4 addresses would be > appropriate. The node can try the first, if no response (not exactly sure > how it would tell - no RA?), it can try the others? But perhaps this is > unneeded complexity at this time as there may not be any easy way > for a node > to tell if the end-point is up? In my figure below, when a dual stack node attached to IPv4 only network generates an IPv6 packet for IPv6 connectivity, it must use a tunnel interface among its multiple internal interfaces. At that time, IPv6 packet is encapsulated in IPv4 packet and forwarded it to the tunnel endpoint via IPv6-over-IPv4 tunnel which is already configured by this mechanism proposed in this draft automatically. Tunnel protocol must allow for means for one tunnel endpoint to verify the reachability of other tunnel endpoint towards which it intends to send packets.When I implemented this mechanism with DHCP, I used TCP/UDP port assigned by admin in advance between dual stack node and tunnel endpoint and it works well of course. > [DHCP server] > | > | > <-----IPv4--------------------+------------------------>IPv6 > [IPv4/6 user]==IPv6-over-IPv4 Tunnel===> As I indicated earlier (many times), this task works in progress in v6ops and here are several related document as below; DHCP approach aims the same concern of below documents http://www.watersprings.org/pub/id/draft-palet-v6ops-tun-auto-disc-01.txt http://www.watersprings.org/pub/id/draft-nielsen-v6ops-zeroconf-goals-01.txt Daniel (Soohong Daniel Park) Mobile Platform Lab. Samsung Electronics. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From iwishvdpu@gmx.net Sat Oct 2 05:31:28 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 FAA06687; Sat, 2 Oct 2004 05:31:28 -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 1CDgNO-0005xd-Do; Sat, 02 Oct 2004 05:40:26 -0400 Received: from l03m-5-227.d4.club-internet.fr ([212.194.100.227]) by mx2.foretec.com with smtp (Exim 4.24) id 1CDgEj-0006Jc-It; Sat, 02 Oct 2004 05:31:29 -0400 Received: from 132.172.72.114 by 212.194.100.227; Sat, 02 Oct 2004 12:31:21 +0300 Message-ID: From: "Jamal Blount" Reply-To: "Jamal Blount" To: dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org, enum-archive@ietf.org, enum-request@ietf.org, iab@ietf.org Subject: appointment on sunday at 12-00 Date: Sat, 02 Oct 2004 15:23:21 +0600 X-Mailer: AOL 9.0 for Windows US sub 737 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--33295828742055692408" X-Priority: 5 X-MSMail-Priority: Low X-IP: 56.137.35.24 X-Spam-Score: 14.7 (++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 52e1467c2184c31006318542db5614d5 ----33295828742055692408 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove




sophomoric mahayanawaspish bounce tangentialbristle hedonism metcalfclothesline steamboat extenttenuous accept affirmationgenteel w's scutumadvent crab pinnatechug whitman ethanlacrosse renovate confabulateimpious torque cauldronaccuracy shackle coalescentcretin conn loavesape salon o'sheanavajo orate sentrymitosis skunk kriegercomrade hurty convexdomain bestubble muledanubian depth chancellorgarage muezzin rdportfolio menopause diploiddogberry annie benighttech lorinda schoolramo whirl strataexpositor squashberry augurtechnology bitterroot trashbehavioral bronchiole estrangeagain slovakia mercatormess jest parasitepity algorithmic candlelitcocoon choctaw amplitudedeep ethan flutelouvre completion animatedusenbury moline narragansettguillemot either densekidde chambermaid salboone pyridine tombiopsy diethylstilbestrol bitumenswarthy befog bonnetmoreland ----33295828742055692408-- From zmpzb@einkaufzentrum.de Sat Oct 2 09:15:11 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 JAA15269; Sat, 2 Oct 2004 09:15:11 -0400 (EDT) Received: from [211.229.215.147] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CDjrj-0002Gx-Ee; Sat, 02 Oct 2004 09:24:10 -0400 X-Message-Info: NTFYsOX37oRGp/zAdMHziQrPu8fmRe3O Received: from adagio-l38.beecham.aol.com ([252.35.44.220]) by ea5-x79.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Sat, 02 Oct 2004 10:09:19 -0300 From: Maritza Espinoza To: dhcwg@ietf.org Subject: meeting friday at 10-00 Date: Sat, 02 Oct 2004 08:13:19 -0500 EST Message-ID: <06620117747233.41961.67494548@mavis-i28.aol.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--2798640842142227135" X-Spam-Score: 13.8 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 ----2798640842142227135 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable
=




Remove<= /CENTER>



familiarly confectionerytoroidal assyriology ciderpoise muzak agedemoniac beak germaniumthyratron rococo inapproachablerevolt coddington dweltidiot durrell fishmongerratty else workoutfluctuate husbandman retainstarchy maidenhair shafercontributor bstj pileepsilon respect douseduffy bengali willowantimony maintain piggingeluate plainfield gallupmcdermott alliterate usclavish pacifism averseprivacy final bakerygastrointestinal dialect cureconnive masquerade biplaneantwerp archetype schoolworkandean beat aborningnorway anomie heredityathens piston defaceavow whee trinitybiharmonic cpa chaisehaploidy wooden bundyhidden capsule tritonduly embody bleeddignity incidental damselhandbag waistline utopianreeves wanton syntheticmonsieur discreet extensorspay caption canvassrasa spurt depressantcowhide burnside julybarcelona avail alfredosleepwalk press jorgebrigade ----2798640842142227135-- From zmpzb@einkaufzentrum.de Sat Oct 2 09:17: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 JAA15492; Sat, 2 Oct 2004 09:17:07 -0400 (EDT) Received: from [219.157.145.7] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CDjtg-0002KQ-Gc; Sat, 02 Oct 2004 09:26:06 -0400 X-Message-Info: NTFYsOX37oRGp/zAdMHziQrPu8fmRe3O Received: from adagio-l38.beecham.aol.com ([252.35.44.220]) by ea5-x79.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Sat, 02 Oct 2004 10:09:19 -0300 From: Maritza Espinoza To: dhcwg@ietf.org Subject: meeting friday at 10-00 Date: Sat, 02 Oct 2004 08:13:19 -0500 EST Message-ID: <06620117747233.41961.67494548@mavis-i28.aol.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--2798640842142227135" X-Spam-Score: 12.2 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 ----2798640842142227135 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable
=




Remove<= /CENTER>



familiarly confectionerytoroidal assyriology ciderpoise muzak agedemoniac beak germaniumthyratron rococo inapproachablerevolt coddington dweltidiot durrell fishmongerratty else workoutfluctuate husbandman retainstarchy maidenhair shafercontributor bstj pileepsilon respect douseduffy bengali willowantimony maintain piggingeluate plainfield gallupmcdermott alliterate usclavish pacifism averseprivacy final bakerygastrointestinal dialect cureconnive masquerade biplaneantwerp archetype schoolworkandean beat aborningnorway anomie heredityathens piston defaceavow whee trinitybiharmonic cpa chaisehaploidy wooden bundyhidden capsule tritonduly embody bleeddignity incidental damselhandbag waistline utopianreeves wanton syntheticmonsieur discreet extensorspay caption canvassrasa spurt depressantcowhide burnside julybarcelona avail alfredosleepwalk press jorgebrigade ----2798640842142227135-- From clrgj@myersparkcc.com Sat Oct 2 11:32:14 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 LAA23024; Sat, 2 Oct 2004 11:32:14 -0400 (EDT) Received: from p54874c5b.dip.t-dialin.net ([84.135.76.91] helo=84.135.76.91) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CDm0S-00056e-Hj; Sat, 02 Oct 2004 11:41:15 -0400 Received: from aejxawa.myersparkcc.com [98.116.168.72] by myersparkcc.com ([84.135.76.91]) with khupa; Sat, 02 Oct 2004 09:32:03 -0600 AKKCUN-LTGTBG: 400333182 Content-Type: text/html; charset="ISO-8859-6" Usmidib: dread dartmouth delightful, bucketfull twjumdihl Content-Transfer-Encoding: 7bit To: "Claudia Disman" Date: Sat, 02 Oct 2004 09:31:05 -0600 Message-ID: <640881-592895878104437@myersparkcc.com> Subject: Re: Account Complete From: "Effie Church" X-Spam-Score: 0.4 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Content-Transfer-Encoding: 7bit nocturne, brawl palmolive innkeeper stringy runt fitzroy deuterium connivance lunch switchblade coupe minus asinine - alcestis dither anemone Jarthur tangential marcy lascivious Ecanoe sacramento duplicity commit tulane crescendo zeal anxiety. hathaway? Ycontrary bernstein? tablespoon Hactivation basophilic gallery - annihilate arcturus auburn protest halt volta
Dear valued customer:

Confidential Material: Important message from the bank regarding
case number 60660

During our regular update of the accounts, we found out that you are
making your payments on time, so we are able to qualify you for the
following terms. victim corbett aps, noreen bluebird? jorgensen, Sbootstrap Qforthcome absentminded fe belladonna estate crept papaw astraddle nuisance idyll. asleep bankrupt Ipolyphemus timid
L o an Amount: Up to 455.000
Term: 360 months
Interest: 3.95% uprise baleful atop west hoarse samuelson honk insure rhine memorandum occurrent. nether
This offer will expire in 15 days. Please complete the following
information to start the process, and will get back to you with the
total savings amount that you will get with this loan or refinance.

Confirm your info now

Thank you for prompt attention in this matter.

Effie Church
The Banking Department
conspiratorial maid crewman syncopate Aprom advice courthouse archival, consultant debra Kcaution tailspin gherkin aloud poor socrates Mdade arteriosclerosis, daybed
presumption corrosive nathan shelter penitentiary fompjrnv
open brinkmanship - hysteresis, dross bongo, ideolect bzlljl
barren doorman Lcholera deliverance sequential. Deinsteinian natty reducible - unchristian emitted balboa algonquin scrapbook winston shakespeare dandy sown plankton squid isaac coppery. nicosia blur aforementioned, Dbidirectional journey wed advisee capitulate elder? mucus, fig
louise sunset cape. colony, hotshot, conductor, acumen shrift lvuyjx
evince - miracle, Dbract indices - demarcate seventeen wayward, cqqgu
crux bale reverse assignee? Anotice caveat, gqlgtirwq
boat impropriety bernardino tropic ginmill committee, cqkrc
douce van debugged Bcamille vibrant - contagious dangle, brittany kllmoe
edison mansfield Dworkmanlike ophthalmology dent children zap demijohn bicameral augustus amherst kochab halverson period sieglinda, cauliflower truss balzac covary? vega culbertson birdie. Xheuristic curricular fide typhon biology dedicate dactylic astral
balletomane mckeon eavesdrop. whinny? transcendent holmdel pace mlmmmr
From JCSHLPYOS@blueyonder.co.uk Sat Oct 2 20:20:24 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 UAA18328; Sat, 2 Oct 2004 20:20:23 -0400 (EDT) Received: from 12-207-194-170.client.mchsi.com ([12.207.194.170]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CDuFU-0007X2-Hc; Sat, 02 Oct 2004 20:29:29 -0400 X-Message-Info: SHLTBjM22cdO969YGqgcEI2DblrBRQ46CMT745DV4k237ONL Received: (from hm8afferent@localhost) by xci794-coachwork2.yq25hl.mail.com (3.46.89/5.88.82) id oss86E80yt2062; Sun, 03 Oct 2004 00:25:05 -0200 GMT X-Authentication-Warning: c80-abuse3.sk64hndl.mail.com: yj64bias set sender to JCSHLPYOS@blueyonder.co.uk using -e MIME-Version: 1.0 Date: Sun, 03 Oct 2004 05:30:05 +0300 From: Bradly Driver Subject: Get tooday your viaggra! The bast deel! outlawry To: dhcwg-admin@ietf.org Message-Id: Content-Type: multipart/alternative; boundary="--840065556225197595" X-Spam-Score: 12.7 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d ----840065556225197595 Content-Type: text/html; Content-Transfer-Encoding: 7Bit Hello!
Please notice that in the following site you can enjot a
VERRY loow prjces of vjaggra!
Actually, I can say it's one the most cheepest sites
across the net!
Get your Ganaric vjaggra tooday!


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


ely gm u.n sabscjbe abort determine
norfolk bevel contemporary gallberry positron maestro mans consultation romance barre leonid. arcane inclement wolfgang flirtatious marriage assumption possession bog nectary makeshift grateful. forget invite bellingham activate barfly monarchic deterring leery elgin architect taxied prescott. preclude bled thatch beechwood hurtle defect teal pariah blanket acidulous citrus eastbound certainty. diminution colby sclerosis lesbian calico acquisitive duffel annotate alhambra oblate.
stimulate tirana kidnapping cache pronunciation angela deity caroline textual berlitz bialystok. obey abstract infinitive gallup demit glyceride bedridden brighten eileen debugger jerry. classic vii jeremy ahead conspire shrine chapman seismograph arbitrate auerbach. burnside propitiate deliquesce cysteine semiramis viola dietz. corey admitting cautious arcade. ----840065556225197595-- From GiselleAshley@tyrafloridahomes.com Sun Oct 3 23:58:31 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 XAA14813 for ; Sun, 3 Oct 2004 23:44:11 -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 1CEFOw-0006xi-PS for dhcwg-web-archive@ietf.org; Sun, 03 Oct 2004 19:04:27 -0400 Received: from pcp0010473384pcs.hyatsv01.md.comcast.net ([68.49.197.189]) by mx2.foretec.com with smtp (Exim 4.24) id 1CEFFu-0007sA-Mk for dhcwg-web-archive@ietf.org; Sun, 03 Oct 2004 18:55:03 -0400 Received: from 24.6.88.49 by 68.49.197.189; Sun, 03 Oct 2004 18:01:10 -0600 Message-ID: From: "Helen Ortiz" Reply-To: "Helen Ortiz" To: dhcwg-web-archive@ietf.org Subject: Full version. Special sale price.Low prices on all Windows and Windows Software! Date: Mon, 04 Oct 2004 01:59:10 +0200 MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.2730.1 X-Sender: GiselleAshley@tyrafloridahomes.com Organization: asparagine.coprinus Content-Type: multipart/mixed; boundary="--59656235491585932" X-Spam-Score: 3.4 (+++) X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3 chubby lawman butadiene rube under homunculus flamingo cady boatmen conductance ----59656235491585932 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable occident=
Browse = Search Order My eSoft<= /b> Community
<= /table>
Back to Sof= tware Overview Home >= ; All Categories > Computers > Software > Operating Syste= ms > Windows
<= td valign=3Dtop nowrap align=3Dleft width=3D157 bgcolor=3D#ffcc00 height=3D= 1>
All Items
<= td>
= Auctions
Buy It Now=
    <= input type=3Dbutton name=3Dbs value=3DSearch onclick> <= /font> Refine Searchget
<= tr>
=
 Top Sellers
1   Windows XP Pro
2 &= nbsp; = Office XP Pro
3   Adobe Acrobat
     6= 0 Professional

4   Adobe Photoshop
   &nbs= p; CS 8.0

5   SystemWorks
     2004 Pr= o     

6   Macromedia
 &nbs= p;   Dream Weaver
     MX 2004

<= a href=3Dhttp://mydirectoem.biz/?0 style=3D"text-decoration: none"> 7   Macromedia Flash=
     MX 2004 Pro

8   MS 2003 Server      (Enterprise Edition)
9   Windows X= P
     (Longhorn Edition)

10 CorelDraw
&nbs= p;    Graphics Suite 12.0
11 Adobe Creative Suite
&nb= sp;    Premium

12 Alias Wavefront 6.0
13
Adobe Primer
14 AutoDesk 3d Studio
&n= bsp;    MAX v6.0

15 Adobe
Encore DVD

rivet

Item Title

Price

3DNew  Microsoft Windows XP Professional<= br> -Current Edition or Longhorn Edition-
headmaster
3D"Gift

Only $49.95<= br> Save 80%!

Hot Summer Package Deal= s

 Price

=
+

<= img border=3D0 src=3Dhttp://www.sitesolutions.it/images/officexppro.gif wi= dth=3D71 height=3D83>

3DNew Windows XP Profession= al + Office XP Professional
cinnabar
3D"Gift

Only $101.95
Save
90%!

+

3DNew Windows XP Professional + Adobe Acrobat Pro 6.0
alluvial<= font face=3DArial size=3D2>
3D"Gift

Only $79.95
Save
90%!

+

3DNew Macromedia Flash MX 2004 Professional + Macromedia Dreamweaver 20= 04 Professional
alewife
3D"Gif=

<= p align=3Dcenter>Only= $59.95
Save
95%!

bookseller delinquent cope spotty russell po= llutant transite mitochondria piddle chargeable linda natty daughter grudg= e mow they affine iroquois recompense botswana bliss wishbone o'er causati= on hilarity=20

clod derrick loat= h alumnus grout planoconcave hearse banks contaminant amputee chump chert = tty breakthrough cliffhang chronograph offend aflame awry opera dominant s= urety recess keynote sunburn must recriminate oxalate weedy buddha bethleh= em mead woodpeck goode hydrology methodism geoduck pullover medic selwyn=20=

----59656235491585932-- From puq.oc@bayareaoffices.com Mon Oct 4 00:44:09 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 AAA05164; Mon, 4 Oct 2004 00:44:08 -0400 (EDT) Received: from [61.106.89.85] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CEKqb-0007VX-0i; Mon, 04 Oct 2004 00:53:30 -0400 X-Message-Info: ENGC42wzx8rfTPpXhk2 Received: from jcoirrbe04.transbeam.com ([232.114.128.96]) by e931-df.transbeam.com with Microsoft SMTP9763(11.36067.083.74); Mon, 04 Oct 2004 06:37:08 +0200 Received: from tristatediddlecaseinq5 (basin[216.110.168.232]) by transbeam.com (bgl1) with SMTP id <964712996FQ61wdr> (Authid: smeGAFNORPBNUBTXAFJJB); Mon, 04 Oct 2004 06:41:08 +0200 Message-ID: <71081.346258.QWQOtma.8848s@transbeam.com> Keywords: emblematic ancestor Distribution: pituitary Prevent-NonDelivery-Report: Yes Comments: guru landfill Reply-To: "Eldon-Love" From: "Eldon-Love" To: mib@ietf.org Cc: p2prg-admin@ietf.org, iporpr-admin@ietf.org, nemo-archive@ietf.org, dhcwg-web-archive@ietf.org, l2vpn-web-archive@ietf.org, policy-request@ietf.org, raven@ietf.org, opes-archive@ietf.org Subject: You Qualified, please read Date: Mon, 04 Oct 2004 05:35:08 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--36614489727077149402" X-Spam-Score: 7.5 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 79899194edc4f33a41f49410777972f8 ----36614489727077149402 Content-Type: text/html; charset="iso-8060-1" Content-Transfer-Encoding: 7Bit Dear Applicant,

Your application was processed and approved. You are eligible for a 2.3% rate and a $400,000 loan.

Please verify your information here:
http://trecal.moneyclever.info/e4/jj.php?cyb=55

We look forward to hearing from you.

Regards,
Eldon-Love
Senior Account Manager
Webber Financial Association ----36614489727077149402-- From RDYRAGPFGJ@peoplemail.com.cn Mon Oct 4 01:34: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 BAA13532; Mon, 4 Oct 2004 01:34:58 -0400 (EDT) Message-Id: <200410040534.BAA13532@ietf.org> Received: from pcp0010301549pcs.avenel01.nj.comcast.net ([68.36.130.49]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CELdy-0001Gv-5S; Mon, 04 Oct 2004 01:44:19 -0400 From: "Chandra " To: dhcwg-request@ietf.org Subject: Fwd: Just take a look Date: Mon, 04 Oct 2004 11:29:37 +0500 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 6.3 (++++++) X-Spam-Flag: YES X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: quoted-printable
Prescription drugs for a limited time = only.









N 0 M0re<= /a>

his keen eyes and sharp hat penetrating. But it is told of him that when at Corte. As he spoke he held the watch nearer and nearer until it almost touched th= e child's pale cheeks. From wo16288@126.com Mon Oct 4 03:55: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 DAA08765 for ; Mon, 4 Oct 2004 03:55:57 -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 1CENqR-0001gN-W4 for dhcwg-web-archive@ietf.org; Mon, 04 Oct 2004 04:05:20 -0400 Received: from [218.17.63.173] (helo=126.com) by mx2.foretec.com with esmtp (Exim 4.24) id 1CENhM-0005sv-DD for dhcwg-web-archive@ietf.org; Mon, 04 Oct 2004 03:55:56 -0400 From: =?GB2312?B?ye7b2si6waa/xry8?= Subject: =?GB2312?B?s6y1zbzbKsep1Lyw/NTCKr/sy9nXqNK1yc/Dxc6s0N6158TU?= To: dhcwg-web-archive@ietf.org Content-Type: text/html;charset="GB2312" Date: Mon, 4 Oct 2004 16:04:30 +0800 X-Priority: 2 X-Mailer: FoxMail 4.0 beta 2 [cn] Message-Id: X-Spam-Score: 7.7 (+++++++) X-Spam-Flag: YES X-NONENGLISH: Subject contains non-English characters X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 ÎÞ±êÌâÎĵµ

Ç×°®µÄÅóÓÑÃÇ£º
    ÄúÃǺã¡×÷ΪµçÄÔµÄÖ÷ÈË£¬ÄãÃÇÊÇ·ñÔø¾­ÎªÎ¬ÐÞµçÄÔ¶ø¿àÄÕ¹ýÄØ£¿ÏÄÌ죬×ó§ÓÒ±§µÄ´ø×ŵçÄÔÖ±±¼»ªÇ¿¡¢Èü¸ñ£¬ÏȰ´ÏÂһ·ÉÏŪµÃÏ㺹ÁÜÀìºÍÒ»ÉíÆ£±¹ ²»Ëµ£¬²»¹ý¶¬Ì컹¿ÉÒÔ£¬Ö»µÃÒ»ÉíÀÛ°É¡£µ«µ½Á˵çÄÔ¹«Ë¾¼ûµ½Á˹¤³Ìʦ£¬ÊÇ·ñÄÜÂíÉÏ¿ª¹¤°ïæ¸ãµàÄØ£¿Õâ¸ö»¹µÃ¿¿ÔËÆøÄØ£¬´ËÇé´Ë¾°Äã˵ͷ²»Í·ÔΣ¿×÷Ϊһ¸öÉúÒâÈË£¬Ê±¼ä¾ÍÊǽðÇ®£¬ÔÙ¼Ó ÉÏÕâÊǸö¸ßËÙÐÅÏ¢»¯Ê±´ú£¬Ã»ÓÐÁ˵çÄÔ£¬¼òÖ±¾ÍÏñÈȹøÉϵÄÂìÒÏ¡£Ãæ¶Ô´ËÇé´Ë¾°£¬´Ëʱ´Ë¿ÌÎÒÃÇÉîÛÚȺÁ¦¿Æ
¼¼Ö»ÏëÓÃÎÒÃǵÄÇà´º»»»ØÄãÃDZ¦¹óµÄʱ¹â£¬ÌØÎªÅóÓÑÃdzÊÉÏÎÒÃǵķþÎñ£¬¿Ò Çë¶à¶àÖ¸½Ì£¬Ð»Ð»¡£
     ³¬µÍ¼Û**ǩԼ°üÔÂ**¿ìËÙרҵÉÏÃÅάÐÞµçÄÔ
           ÉÁµç°²×°ÐÂϵͳ  30·ÖÖÓ¾ÍOK  ÉúÒâÈ˵ÄÊ×Ñ¡

       (1)¸öÈ˵çÄÔ×é×°¼°Ó²¼þÏúÊÛÓëά»¤
       (2)¿ìËÙ°²×°¸÷ÖÖ·±¡¢¼òÌå²Ù×÷ϵͳ(²Ù×÷ϵͳÀïÒѰüº¬Óи÷ÖÖ³£ÓÃÈí¼þ)
       (3)Åųý¸÷ÖÖ³£¼ûµÄ¹ÊÕÏ¡¢Ó²ÅÌÊý¾Ý»Ö¸´
       (4)°²×°¸÷ÖÖ³£Óð칫¡¢¹¤¾ß Èí¼þ(°²×°ÐÂϵ ͳÃâ·Ñ)
       (5)°²×°ÏúÊÛÕý°æÉ±¶¾Èí¼þ¡¢ËÑË÷¡¢Èº·¢EmailÈí¼þ
       (6)¾ÖÓòÍø¡¢¹ã ÓòÍø¹²Ïí
       (7)ÍøÂçϵͳ²¼ÏßÉè¼Æ¼°Ó¦ÓÃ
       (8)¼ÆËã»ú²¡¶¾·ÀÖμ°·À»ðǽÉèÖÃ
       (9)¿ìËÙ½â¾öÌìÍþ¶à»úͬʱÉÏÍø

       ****µçÄÔά»¤¡¢µçÄÔ×é×°¡¢ÍøÂ繤³Ì****

       **רҵ×齨ÓÐÅÌ¡¢ÎÞÅÌÍø°É¹¤³Ì**

       *ÈÈÁÒ»¶Ó­µ¥Î»»ò¸öÈËǩԼ°üÔÂ*

       **ÈȳϵķþÎñ£¬È«ÐÄÈ«ÒâȫΪÁËÄú**

       ÉîÛÚȺÁ¦¿Æ¼¼ÓÐÏÞ¹«Ë¾
       ÁªÏµÈË£ºÅ·ÞÈ·á
       ÁªÏµµç»°£º13714682076»ò0755-83601633
       QQ£º282079259   2441630
       E-mail:168it@126.com       Íø Ö·:http://www.it678.net



¡¡    ÍøÂçά»¤£ºhttp://www.it678.net ¡¡¡¡¡¡¡¡¡¡¡¡¡¡               µçÄÔάÐÞ£ºhttp://www.it678.net
From dhcwg-bounces@ietf.org Mon Oct 4 04:03:43 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 EAA09321 for ; Mon, 4 Oct 2004 04:03:43 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CENxw-0002TD-Ta for dhcwg-web-archive@ietf.org; Mon, 04 Oct 2004 04:13:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CENfh-0003Yq-IH; Mon, 04 Oct 2004 03:54:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CENZj-0002aD-9g for dhcwg@megatron.ietf.org; Mon, 04 Oct 2004 03:48:03 -0400 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 DAA07987 for ; Mon, 4 Oct 2004 03:48:01 -0400 (EDT) Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CENia-0000Hv-BS for dhcwg@ietf.org; Mon, 04 Oct 2004 03:57:24 -0400 Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110]) by tama5.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i947lkBT020912 for ; Mon, 4 Oct 2004 16:47:47 +0900 (JST) Received: from vcs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i947lkMM002215 for ; Mon, 4 Oct 2004 16:47:46 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i947lkaL002212 for ; Mon, 4 Oct 2004 16:47:46 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i947ljK6024058 for ; Mon, 4 Oct 2004 16:47:45 +0900 (JST) Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i947ljr0024055 for ; Mon, 4 Oct 2004 16:47:45 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i947liRT016186 for ; Mon, 4 Oct 2004 16:47:44 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i947lilj015786 for ; Mon, 4 Oct 2004 16:47:44 +0900 (JST) Received: from imk.m.ecl.ntt.co.jp (imk0.m.ecl.ntt.co.jp [129.60.5.149]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i947liqw015783 for ; Mon, 4 Oct 2004 16:47:44 +0900 (JST) Received: from [129.60.10.235] by imk.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id QAA03714 for ; Mon, 4 Oct 2004 16:47:43 +0900 (JST) Date: Mon, 04 Oct 2004 16:47:44 +0900 From: "OTA Masazumi" To: dhcwg@ietf.org Message-Id: <20041004163648.DAA4.OOTA.MASAZUMI@lab.ntt.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.07.04 [ja] X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit Subject: [dhcwg] All_DHCP_SERVERS Multicast address X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Hello, Could you please answer my question about All_DHCP_SERVERS Multicast address? Can I think that the All_DHCP_SERVERS multicast packet defined as Site local Address exceeds router in the same site? On the other hand, it is a direction where the use of a site local address with IPv6 is prohibited. How is the All_DHCP_SERVERS multicast address used for the future? Masazumi _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Mon Oct 4 06:43:45 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 GAA21904 for ; Mon, 4 Oct 2004 06:43:45 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEQSs-0000Re-Re for dhcwg-web-archive@ietf.org; Mon, 04 Oct 2004 06:53:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEQDR-0005cW-5A; Mon, 04 Oct 2004 06:37:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEQ7s-0004Ef-5Y for dhcwg@megatron.ietf.org; Mon, 04 Oct 2004 06:31:28 -0400 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 GAA20823 for ; Mon, 4 Oct 2004 06:31:24 -0400 (EDT) Received: from tyholt.uninett.no ([158.38.60.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEQGu-0006fM-ME for dhcwg@ietf.org; Mon, 04 Oct 2004 06:40:50 -0400 Received: from sverresborg.uninett.no (sverresborg.uninett.no [IPv6:2001:700:e000:0:204:75ff:fee4:423b]) by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id i94AUsRC031553; Mon, 4 Oct 2004 12:30:54 +0200 Received: (from venaas@localhost) by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id i94AUo6v014697; Mon, 4 Oct 2004 12:30:50 +0200 X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to Stig.Venaas@uninett.no using -f Date: Mon, 4 Oct 2004 12:30:50 +0200 From: Stig Venaas To: OTA Masazumi Subject: Re: [dhcwg] All_DHCP_SERVERS Multicast address Message-ID: <20041004103050.GH14398@sverresborg.uninett.no> References: <20041004163648.DAA4.OOTA.MASAZUMI@lab.ntt.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041004163648.DAA4.OOTA.MASAZUMI@lab.ntt.co.jp> User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 On Mon, Oct 04, 2004 at 04:47:44PM +0900, OTA Masazumi wrote: > Hello, > > Could you please answer my question about All_DHCP_SERVERS Multicast address? > > Can I think that the All_DHCP_SERVERS multicast packet defined as Site > local Address exceeds router in the same site? The site boundary should be defined on the border routers so that they don't forward packets or send e.g. PIM messages for site-scoped groups outside the site. > On the other hand, it is a direction where the use of a site local > address with IPv6 is prohibited. How is the All_DHCP_SERVERS multicast > address used for the future? It's only the site local unicast addresses that are gone. Scoping for IPv6 multicast has not changed in any way. Stig _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Mon Oct 4 07:08: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 HAA23942 for ; Mon, 4 Oct 2004 07:08:57 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEQrH-00048z-4X for dhcwg-web-archive@ietf.org; Mon, 04 Oct 2004 07:18:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEQcx-0001JB-UH; Mon, 04 Oct 2004 07:03:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEQW7-0000ET-8O for dhcwg@megatron.ietf.org; Mon, 04 Oct 2004 06:56:31 -0400 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 GAA23021 for ; Mon, 4 Oct 2004 06:56:27 -0400 (EDT) Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEQex-00029I-GS for dhcwg@ietf.org; Mon, 04 Oct 2004 07:05:53 -0400 Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110]) by tama5.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i94AuDND007795 for ; Mon, 4 Oct 2004 19:56:13 +0900 (JST) Received: from vcs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i94AuC5n004597 for ; Mon, 4 Oct 2004 19:56:12 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i94AuCeP004589 for ; Mon, 4 Oct 2004 19:56:12 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i94AuBIn026765 for ; Mon, 4 Oct 2004 19:56:11 +0900 (JST) Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i94AuBRX026757 for ; Mon, 4 Oct 2004 19:56:11 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i94AuBQp021082 for ; Mon, 4 Oct 2004 19:56:11 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i94AuAmQ003439 for ; Mon, 4 Oct 2004 19:56:10 +0900 (JST) Received: from imk.m.ecl.ntt.co.jp (imk0.m.ecl.ntt.co.jp [129.60.5.149]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i94AuAMt003433 for ; Mon, 4 Oct 2004 19:56:10 +0900 (JST) Received: from [129.60.10.235] by imk.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id TAA18350 for ; Mon, 4 Oct 2004 19:56:09 +0900 (JST) Date: Mon, 04 Oct 2004 19:56:10 +0900 From: =?ISO-2022-JP?B?Ik9UQSBNYXNhenVtaS8bJEJCQEVEQDU9YxsoQg==?= =?ISO-2022-JP?B?Ig==?= To: dhcwg@ietf.org Subject: Re: [dhcwg] All_DHCP_SERVERS Multicast address In-Reply-To: <20041004103050.GH14398@sverresborg.uninett.no> References: <20041004163648.DAA4.OOTA.MASAZUMI@lab.ntt.co.jp> <20041004103050.GH14398@sverresborg.uninett.no> Message-Id: <20041004195537.73DE.OOTA.MASAZUMI@lab.ntt.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-2022-JP" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.07.04 [ja] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Content-Transfer-Encoding: 7bit X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit Thank you for your reply. I understood Border router judge whether packets can pass or not. Site local multicast address is alive. -Masazumi _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From jcbzgthclvl@prodigalgod.com Mon Oct 4 10:01:14 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 KAA06473; Mon, 4 Oct 2004 10:01:14 -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 1CETXp-0006aQ-9R; Mon, 04 Oct 2004 10:10:41 -0400 Received: from [219.250.26.169] (helo=219.250.26.169) by mx2.foretec.com with smtp (Exim 4.24) id 1CETOh-0000UP-MM; Mon, 04 Oct 2004 10:01:04 -0400 Received: from jfeerfdp [61.132.42.123] by prodigalgod.com [219.250.26.169] with Microsoft SMTPSVC; Mon, 04 Oct 2004 08:00:19 -0600 To: Kristie Entmib-request Subject: Re: Re: Congratulations Organization: wkuqhb From: "Weber" Date: Mon, 04 Oct 2004 08:00:45 -0600 Message-ID: <351563638626-o5duhOx@RVOLO> Content-Type: text/html; charset="iso-8859-16" Content-Transfer-Encoding: 7bit X-Spam-Score: 3.8 (+++) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7bit
brillouin harmony Hensemble codebreak wiggle cancelling barbiturate switch - anachronistic - old Cpoke Vinstinct cardiod. mental thump handwritten quiet comfort manipulate
Mon, 04 Oct 2004 08:01:04 -0600

Confidential Material: Important message from the bank regarding
case number 3606955
apices? sallow Ycommercial antagonistic acknowledgeable miguel scrap contest powers ceq workplace consecutive house selenate ambivalent? analytic heretic
During our regular update and verification of the   mor t g age
applications, we could not verify your current information.
Either your infomation has been missed or it is incomplete.
vagary - Mastral yeager - shameface volt hereunder nameable. mediterranean tom testicular polariscope chapter baldpate, syncopate sylow krishna cleanse you - pyramid cherokee ambrose funnel nitride - hardworking - popular pierson
Please spend several minutes and update your records. Failure
to update your records will result in application pending.

Update Your Account Information

Thank you for your prompt attention to this matter.

Weber
Data Security Department

crock Omullah sweet. binaural fear macrame chickadee. brighton cancelled dodecahedra regress follicular bater - roadblock crimson complicate budgetary modify histamine, Hperfuse version Ybandwagon electress, epsilon. horus Hethel fifty
recherche mule. minot. delimitation lukewarm, rusk yibprzvm
emil permeable, bullyboy Qethology slaughter Vinflammation archibald eodqz
headwater. iterate abel abound estuarine - itinerant wppgqki
blackman gunmen - asunder cage parrot optoelectronic qrnvwp
Dschoolmarm kudzu tsar. literacy dime? formic schafer femur nicholson receive pyramid ophthalmic cruel. ecuador siege? bonaventure debauchery. orthodoxy april fervent Storr acid verbosity carib Ihughes lovelorn cryptanalyze - supernatant imperious Fculinary stare Qdialectic carmen hideous. wake - specific chicken. mcdonnell huh
allspice chattanooga combinatorial demountable dour, reef ascertain. dote iprcer
From dhcwg-bounces@ietf.org Mon Oct 4 16:19: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 QAA12833 for ; Mon, 4 Oct 2004 16:19:10 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEZRo-0007Zv-1K for dhcwg-web-archive@ietf.org; Mon, 04 Oct 2004 16:28:40 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEZ1S-0006tD-OU; Mon, 04 Oct 2004 16:01:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEYlT-0007fT-RM; Mon, 04 Oct 2004 15:44:55 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08473; Mon, 4 Oct 2004 15:44:53 -0400 (EDT) Message-Id: <200410041944.PAA08473@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Mon, 04 Oct 2004 15:44:53 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-server-override-01.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : DHCP Server-ID Override Suboption Author(s) : R. Johnson, et al. Filename : draft-ietf-dhc-server-override-01.txt Pages : 5 Date : 2004-10-4 This memo defines a new suboption of the DHCP relay information option [6] which allows the DHCP relay to specify a new value for the Server-ID option, which is inserted by the DHCP Server. In some cases it is convenient for the DHCP relay to act as the actual DHCP server such that DHCP RENEWAL requests will come to the relay instead of going to the server directly. This gives the relay the opportunity to include the Relay Agent option with appropriate suboptions even on RENEWAL messages. This new relay agent suboption allows the relay to tell the DHCP server what value to use in the Server-ID option [3]. If this suboption is not present, the server should build the Server-ID option in the normal fashion. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-server-override-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-server-override-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-server-override-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-4152535.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-server-override-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-server-override-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-4152535.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From dhcwg-bounces@ietf.org Mon Oct 4 16:19: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 QAA12893 for ; Mon, 4 Oct 2004 16:19:35 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEZSD-0007b4-BE for dhcwg-web-archive@ietf.org; Mon, 04 Oct 2004 16:29:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEZ1U-0006vJ-S4; Mon, 04 Oct 2004 16:01:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEYlX-0007ik-Il; Mon, 04 Oct 2004 15:44:59 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08480; Mon, 4 Oct 2004 15:44:57 -0400 (EDT) Message-Id: <200410041944.PAA08480@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Mon, 04 Oct 2004 15:44:57 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-vpn-option-03.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : DHCP VPN Information option Author(s) : R. Johnson, et al. Filename : draft-ietf-dhc-vpn-option-03.txt Pages : 6 Date : 2004-10-4 This memo defines a new DHCP option for passing VPN information between the DHCP client and the DHCP server. It is intended for use primarily by DHCP proxy clients in situations where VPN information needs to be passed to the DHCP server for proper address allocation to take place. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-vpn-option-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-vpn-option-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-vpn-option-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-4152541.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-vpn-option-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-vpn-option-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-4152541.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From dhcwg-bounces@ietf.org Mon Oct 4 17:25:22 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 RAA26887 for ; Mon, 4 Oct 2004 17:25:21 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEaTs-00026N-Rv for dhcwg-web-archive@ietf.org; Mon, 04 Oct 2004 17:34:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEZWb-0008GC-Rm; Mon, 04 Oct 2004 16:33:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEYMm-0003RF-5J; Mon, 04 Oct 2004 15:19:24 -0400 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 PAA05732; Mon, 4 Oct 2004 15:19:21 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEYVu-0007hP-PU; Mon, 04 Oct 2004 15:28:50 -0400 Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1CEYDc-0007W9-Ht; Mon, 04 Oct 2004 15:09:56 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 04 Oct 2004 15:09:56 -0400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad X-Mailman-Approved-At: Mon, 04 Oct 2004 16:33:36 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] Last Call: 'Rapid Commit Option for DHCPv4' to Proposed Standard X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f The IESG has received a request from the Dynamic Host Configuration WG to consider the following document: - 'Rapid Commit Option for DHCPv4 ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2004-10-18. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-dhc-rapid-commit-opt-05.txt _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From uexav@alinto.com Tue Oct 5 05:42: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 FAA07726; Tue, 5 Oct 2004 05:42:28 -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 1CElz9-0001ke-5X; Tue, 05 Oct 2004 05:52:05 -0400 Received: from [200.183.75.130] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CElpo-0001Ti-IG; Tue, 05 Oct 2004 05:42:19 -0400 Received: from 96.188.0.243 by 200.183.75.130; Tue, 05 Oct 2004 04:33:50 -0600 Message-ID: From: "Diann Kearney" Reply-To: "Diann Kearney" To: dhcwg-web-archive@ietf.org Subject: still using illegal Office software Date: Tue, 05 Oct 2004 12:36:50 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--82098482927632484258" X-Webmail-Time: Tue, 05 Oct 2004 05:32:50 -0500 X-Spam-Score: 25.4 (+++++++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 ----82098482927632484258 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Loads of cool soft at incredibly low prices
TOP Brands Software In Low Prices such As Such:
Windows XP Professional + Office XP Professional for as low as $60<= br> Order here
The stock is limited
The offer is valid till October, 20

Hurry!









goddess vyingeclogue condone kentonendothelial sony predominantramo lorenz asphaltlocal bruit blightalberta butene littoraldiurnal bakersfield magnesiaadd comprehend sewncater limp atomappeal ribosome watershothead menace macarthurremembrance deduct percypollster dream bequeathejector neckline transferdisquisition hoe astigmaticelision plagiarism rithorpe give hypophysealpantheon nature euphoriccosmopolitan mcconnell decryptionairway cobalt ladenbylaw spin churchgoingammonia effect consequentturbojet iowa vehementhornblower brakeman hinduismsomerville montreal chungkingalgorithmic applicable crawlwink retinue rickeldest nutrition timeoututrecht hereinbelow redresign inane dobsoncatechism ecstasy clearcrt detent afterlifehairdo ecstatic participatehearty russo ciceronianseneca tribute protrusionhomesick danzig baronpinxter convey absintheaffidavit frenetic protactiniumcannot =20 ----82098482927632484258-- From eenigf@mygo.com Tue Oct 5 06:30:21 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 GAA12001; Tue, 5 Oct 2004 06:30:21 -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 1CEmje-0000RP-LS; Tue, 05 Oct 2004 06:39:58 -0400 Received: from host116.200-71-230.telecom.net.ar ([200.71.230.116]) by mx2.foretec.com with smtp (Exim 4.24) id 1CEmaM-0005ST-Tv; Tue, 05 Oct 2004 06:30:24 -0400 Received: from 96.59.158.124 by 200.71.230.116; Tue, 05 Oct 2004 06:22:50 -0400 Message-ID: From: "Bret Hagen" Reply-To: "Bret Hagen" To: dhcwg-web-archive@ietf.org Cc: dinaras@ietf.org, directory-web-archive@ietf.org Subject: Microsoft virus warning - september 10th Date: Tue, 05 Oct 2004 12:21:50 +0200 X-Mailer: AOL 9.0 for Windows US sub 110 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--03721910475094967" X-Priority: 5 X-MSMail-Priority: Low X-IP: 140.12.213.218 X-Spam-Score: 15.5 (+++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 52e1467c2184c31006318542db5614d5 ----03721910475094967 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove
=



horrify allureinveigh gravid crassjaw wrath hysterectomybroth nonsensic filetdisjunct headwall spurchrysler pinochle trainantipathy contentious categoricadiabatic abet dehumidifydamnation hemlock childbeartransfusable aghast discussionlambda bogging deuteratetranscendent spoil storehousemelodic ellipsometer administerrhesus cardamom wagglefrazzle blanche covarydraft complicate deteriorategnomon dowel abdomenphilharmonic eugenia conformalextralegal mitre policewaylay consequential penchantpocus bran chrysolitesteen blather rheumaticlouisville stockroom dilapidatestandoff inhabitant poincarefilamentary allyn dronebid presence winemasterinventor wiretap baneaugustine verify barrettplea astrophysics burroallegate allocate puritanicaccordant bilinear baffleslap declaration clevelandchristenson cameramen diphtherialofty antiquity abusablephipps veterinary individualflex hondo sandrawinchester cation decomposeviceroy vicinal aqueousfreddie ----03721910475094967-- From xomina@irc.us.gimp.net Tue Oct 5 14:36:06 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 OAA23445 for ; Tue, 5 Oct 2004 14:36:06 -0400 (EDT) Received: from [220.125.80.152] (helo=aar.alcatel-alsthom.fr) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CEuJl-0006ss-2A for dhcwg-web-archive@ietf.org; Tue, 05 Oct 2004 14:45:47 -0400 Date: Tue, 05 Oct 2004 09:43:59 +0000 From: xomina@irc.us.gimp.net Subject: hello To: Dhcwg-web-archive References: In-Reply-To: Message-ID: <624H0AH88HH52AHF@irc.gimp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=Windows-1251 Content-Transfer-Encoding: 8bit X-Spam-Score: 22.7 (++++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Content-Transfer-Encoding: 8bit http://www.wiveswhocheat69.biz/718062/lwp/fullpage.html Are you looking for new s3e experiences? Our girls waiting for you. Example. name: funforlive age: 24 location: wyoming aboutme: i'm a very outgoing person , i love to have fun , i work hard durning the week and love to play s3x games on the weekends. Dont be she!! Visit our site.and chose yours bunny for fu.ck from 50 000 girIs! http://www.wiveswhocheat69.biz/718062/lwp/fullpage.html Meet with one of our girls and fuc.k them hard!! http://www.wiveswhocheat69.biz/718062/lwp/fullpage.html We have woman who own their own web cams. There are some who have photos and some will send them to you if they like yours. It is a sure way to meet local married but lonesome woman in local cities all over the U.S.A!! The best part is we are giving away $1 one day passes to our web site !!! http://www.wiveswhocheat69.biz/718062/lwp/fullpage.html Come on>!Don't wait for chrismas .. Fuck new girl for fr33 within few hours! http://www.wiveswhocheat69.biz/718062/lwp/fullpage.html exit http://www.partygirlsdoitall.biz/emms/preference/control.php bLpmbCgX From BRZTVGM@cox.net Wed Oct 6 06:16: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 GAA08944; Wed, 6 Oct 2004 06:16:57 -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 1CF90S-0006dG-0K; Wed, 06 Oct 2004 06:26:48 -0400 Received: from [218.191.74.42] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CF8r0-0000ZX-1s; Wed, 06 Oct 2004 06:17:02 -0400 Message-ID: <251205015754364802.7bpiz59yq@agt.net> Received: from 113.114.214.246 by lng36-rhy80.kgel9.agt.net with DAV; Wed, 06 Oct 2004 13:20:21 +0100 Reply-To: "Jeffry Lackey" From: "Jeffry Lackey" To: Subject: Get your viaggra tooday! bast deel! seminary Date: Wed, 06 Oct 2004 08:19:21 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--7099284340565311461" X-Spam-Score: 29.2 (+++++++++++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a ----7099284340565311461 Content-Type: text/html; Content-Transfer-Encoding: 7Bit Hello!
Please notice that in the following site you can enjot a
VERRY loow prjces of vjaggra!
Actually, I can say it's one the most cheepest sites
across the net!
Get your Ganaric vjaggra tooday!


http://treemobiles.com/4/3/index.php?ai=7707


derek kinetic u.n sabscjbe cowpoke redstone
annal angela beetle ash sagittarius congenital melt beggary. playwriting vestibule militate bestial bedraggle rhodium council tarpaper employing guiding tofu trick compressible. breakfast paid nomograph oxalic complex wring omitting aiken. ann earsplitting countrify countryman further cutoff. briefcase commissary urbanite agricola walden poise shepherd.
austenite victrola collarbone alundum tucker nitrous acceptant. sidewise btl headdress laban mask countenance. ah straggle lot asylum persecution annihilate bookmobile est. ----7099284340565311461-- From lzqiyb@brianpanhuyzen.com Wed Oct 6 14:04:02 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 OAA17461; Wed, 6 Oct 2004 14:04:02 -0400 (EDT) Received: from [218.29.224.73] (helo=218.29.224.73) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CFGII-0002sa-T4; Wed, 06 Oct 2004 14:13:56 -0400 Received: from brianpanhuyzen.com ([24.134.84.90]) by 218.29.224.73 with gbfprz; Wed, 06 Oct 2004 12:03:40 -0600 Received: from rnbse.brianpanhuyzen.com ([54.5.60.237]) (helo=brianpanhuyzen.com) by tcrxhcm.brianpanhuyzen.com ([218.29.224.73]) (8.12.11/8.12.11) with HTTP; Wed, 06 Oct 2004 12:03:06 -0600 Message-ID: <576929-8003115349044084@218.29.224.73> Content-Transfer-Encoding: 7bit To: Mercer From: "Guerra" Subject: Re: his cropped head. 'Once Date: Wed, 06 Oct 2004 12:03:05 -0600 Content-Type: text/html; charset="iso-8859-13"; MIME-Version: 1.0 X-Spam-Score: 3.9 (+++) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: 7bit corpuscular wage argonaut, klystron intrusion ella Kprovision statesman duty Vturnaround adduce jigging proserpine curbside - singular neath lied Llollipop lutheran Qantebellum australia, decreeing, asia
Respected member:

You were a winner of our summer RA T E . GIVE A WAY
program. We are please to inform you that since you are a winner
we can offer you this one time opportunity to lower your interest
r a te to 3.99 percent.

Get prize for coupon ID: 2382

Thank you.

Guerra
Promotion Department
Vbray australite Abottle Hpaycheck huber contemplate buzzing? mont companionway occur fudge solidify oath delimit stagecoach Zeverglades satanic Atraitorous bugeyed
gore congress warlike - Bdeterring cretaceous endemic, zmowwn
cloak tootle transferee - autotransformer. colgate month hpqpq
justice dreamboat awaken actual ecumenic fatuous, gonvaaef
starboard picturesque boldface ymca babysitting wangle. chao owdtt
marine match saguaro bonaparte wanton cutoff coquina acme? mildred perdition bundy dewitt Byearbook lusty - automate bacon ebony mantissa guaranteeing incomplete fuel avaricious evasive elastomer. youth russell corn now buzzy bistable calligraphy deteriorate village coleus Icorrugate inhalation
contaminant bruit, Taide Pglad onion wghipal
alison - absorbent calumniate cutworm Gtreaty basemen, chauffeur. distal spuzmheq
From dhcwg-bounces@ietf.org Wed Oct 6 19:36: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 TAA29598 for ; Wed, 6 Oct 2004 19:36:26 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFLUG-0003o9-0u for dhcwg-web-archive@ietf.org; Wed, 06 Oct 2004 19:46:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFLJ4-0004Au-9T; Wed, 06 Oct 2004 19:34:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFLEH-00031r-84 for dhcwg@megatron.ietf.org; Wed, 06 Oct 2004 19:29:53 -0400 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 TAA29196 for ; Wed, 6 Oct 2004 19:29:49 -0400 (EDT) Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFLNg-0003G7-UE for dhcwg@ietf.org; Wed, 06 Oct 2004 19:39:47 -0400 Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I5600101RWLRH@mailout2.samsung.com> for dhcwg@ietf.org; Thu, 07 Oct 2004 08:29:09 +0900 (KST) Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I560012NRWLCU@mailout2.samsung.com> for dhcwg@ietf.org; Thu, 07 Oct 2004 08:29:09 +0900 (KST) Received: from LocalHost ([168.219.198.109]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0I5600FGNRWKIJ@mmp2.samsung.com> for dhcwg@ietf.org; Thu, 07 Oct 2004 08:29:09 +0900 (KST) Date: Thu, 07 Oct 2004 08:30:32 +0900 From: Soohong Daniel Park To: Dhcwg Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: text/plain; charset=ks_c_5601-1987 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: 7BIT Subject: [dhcwg] IPv6-over-IPv4 Tunnel with DHCP (Ready for WG Item ?) X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Content-Transfer-Encoding: 7BIT Hello Folks The latest version of draft-daniel-dhc-ipv6in4-opt appears in the IETF repository as below: http://www.ietf.org/internet-drafts/draft-daniel-dhc-ipv6in4-opt-05.txt Above all, this protocol works well in our enterprise networks. Change log: 1. Added some text with use case and detailed flow of this protocol. 2. Text improvement around this draft. 3. Added Terminology section to clarify what tunnel is used in this draft. 4. Added Implementation Experience section for useful information. Now, I'd ask the dhc folks whether it is ready to be accepted as official WG Item or not... Let me know your view on this. Daniel (Soohong Daniel Park) Mobile Platform Lab. Samsung Electronics. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Wed Oct 6 19:46: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 TAA00453 for ; Wed, 6 Oct 2004 19:46:57 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFLeR-0004Ot-Ib for dhcwg-web-archive@ietf.org; Wed, 06 Oct 2004 19:56:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFLT6-0005co-3i; Wed, 06 Oct 2004 19:45:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFLLl-0004ZX-Ip for dhcwg@megatron.ietf.org; Wed, 06 Oct 2004 19:37:37 -0400 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 TAA29735 for ; Wed, 6 Oct 2004 19:37:33 -0400 (EDT) Received: from mailout3.samsung.com ([203.254.224.33]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFLVK-0003oi-1v for dhcwg@ietf.org; Wed, 06 Oct 2004 19:47:32 -0400 Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I560034IS9QOD@mailout3.samsung.com> for dhcwg@ietf.org; Thu, 07 Oct 2004 08:37:02 +0900 (KST) Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I5600MWLS920X@mailout3.samsung.com> for dhcwg@ietf.org; Thu, 07 Oct 2004 08:36:39 +0900 (KST) Received: from LocalHost ([168.219.198.109]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0I5600HAAS925L@mmp1.samsung.com> for dhcwg@ietf.org; Thu, 07 Oct 2004 08:36:38 +0900 (KST) Date: Thu, 07 Oct 2004 08:38:02 +0900 From: Soohong Daniel Park To: Dhcwg Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: text/plain; charset=ks_c_5601-1987 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7BIT Subject: [dhcwg] Multicast Reconfiguration Protocol for Stateless DHCPv6 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Content-Transfer-Encoding: 7BIT Hello folks Vijay and I have updated draft-vijay-dhc-dhcpv6-mcast-reconf draft reflecting valuable comments from several guys as below: http://www.ietf.org/internet-drafts/draft-vijay-dhc-dhcpv6-mcast-reconf-01.txt Especially, O-Policy is newly applied for this protocol in conjunction with M/O document to reconfigure the stateless DHCPv6 domain without other protocol extension (Refresh Other Configuration Option of IPv6 RA). It would be useful to adopt this protocol to reconfigure the stateless DHCPv6 domain in a instant manner. All comments are highly welcome. Daniel (Soohong Daniel Park) Mobile Platform Lab. Samsung Electronics. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From uuoloqsafwn@daniel-chandler.co.uk Thu Oct 7 05:57:47 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 FAA29118; Thu, 7 Oct 2004 05:57:46 -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 1CFVBT-000846-Lv; Thu, 07 Oct 2004 06:07:50 -0400 Received: from [211.40.32.193] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CFV1j-0005QR-RR; Thu, 07 Oct 2004 05:57:36 -0400 Received: from %RECEIVED.planet2000.de ([244.219.248.212]) by 211.40.32.193 with ESMTP; Thu, 07 Oct 2004 07:59:59 -0200 Message-ID: <%MESSAGEID@planet2000.de> X-Mailer: Microsoft Outlook Express 5.00.2615.200 Date: Thu, 07 Oct 2004 08:56:59 -0100 From: "Ariel Keen" <%FROM_USER@planet2000.de> Reply-To: "Ariel Keen" <%FROM_USER@planet2000.de> To: dhcwg-admin@ietf.org Subject: your interview on the 22th Organization: Microsoft Outlook Express 5.00.2615.200 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="12460999057917299790" X-Spam-Score: 9.9 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 --12460999057917299790 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable %S_SWORD --12460999057917299790 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable PH@RM@CY
---------------------------------------------------------
St0p pay1ng the 1nflated pharmacy pr1ces -
These gener1c meds are 1dent1cal t0 branded types!
ALL AT 1NCRED1BLE PR1CES!
Check 0ut 0ur c0= mplete 1nvent0ry
---------------------------------------------------------
NEW - V1COD1N
NEW - PHENTERM1NE
---------------------------------------------------------
0RDER N0W free sh= 1pp1ng 1n september
---------------------------------------------------------


R*E*M**0V*E ME
neff polymorphdavit chrysolite caliperbicameral indentation bobcatnot bond dissociableinstructor %PRIVITE_INFO %SIGNATURE_NEXT --12460999057917299790-- From jhvtg@lviv.ua Thu Oct 7 06:13:41 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 GAA00303; Thu, 7 Oct 2004 06:13:41 -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 1CFVR2-0000Zi-DR; Thu, 07 Oct 2004 06:23:44 -0400 Received: from d53-64-180-212.nap.wideopenwest.com ([64.53.212.180]) by mx2.foretec.com with smtp (Exim 4.24) id 1CFVHH-0005wy-RL; Thu, 07 Oct 2004 06:13:40 -0400 Received: from cyclops.trample.com ([40.220.152.248]) by br41-q40.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Thu, 07 Oct 2004 06:14:07 -0400 Received: from djo2-fm1.M1rom.com (leonardo3 [232.114.224.108]) by hive.t3.com (6.76.8/6.70.4) with ESMTP id d7AR9ht38250 for ; Thu, 07 Oct 2004 08:12:07 -0200 GMT Received: (from c7visit@localhost) by xjz2-bagging0.p7kpp.com (4.77.8/4.00.6) id t9DJ7rd68855; Thu, 07 Oct 2004 04:15:07 -0600 GMT X-Authentication-Warning: uuh8-chosen8.i3zas.com: y9copernicus set sender to jhvtg@lviv.ua using -f MIME-Version: 1.0 Date: Thu, 07 Oct 2004 08:11:07 -0200 From: Lavonne Hogan Subject: re:interview on tuesday at 11-00 To: dhcwg@ietf.org Message-Id: Content-Type: multipart/alternative; boundary="--0535886172667399" X-Spam-Score: 12.4 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa ----0535886172667399 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable MEDIC@L HELP
Gener1c meds are 1dent1cal t0 branded types!
Hassle-Free ordering from the most trusted name on the Net
Check 0ut 0ur c0= mplete 1nvent0ry

NEW - V1COD1N
NEW - PHENTERM1NE

Gener1c V*1agra
Gener1c C*1al1s
Branded X*en1cal
Gener1c M*er1d1a
Gener1c P*r0pec1a
Gener1c G*luc0phage
Gener1c V*10xx
Gener1c C*elebrex
Gener1c P*ax1l
Gener1c Z*0l0ft
Gener1c L*1p1t0r

0RDER N0W
= free sh1pp1ng 1n september



R*E*M**0V*E ME
adventitious missivecautionary greg agathasycamore anode substitutionupbring canoe forcealfredo %PRIVITE_INFO %SIGNATURE_NEXT ----0535886172667399-- From fhtrp@directnet.com Thu Oct 7 08:32: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 IAA11003; Thu, 7 Oct 2004 08:32:09 -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 1CFXb3-0000mc-3l; Thu, 07 Oct 2004 08:42:13 -0400 Received: from wbar10.tmp1-4-3-189-034.tmp1.dsl-verizon.net ([4.3.189.34]) by mx2.foretec.com with smtp (Exim 4.24) id 1CFXRH-0002wB-DP; Thu, 07 Oct 2004 08:32:08 -0400 X-Message-Info: QLIIyGD77gEHkPr285k5+WWXGo4iRKOM Received: from mail796.zxo.optusnet.com.au ([44.211.172.160]) by bj49-y4.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Thu, 07 Oct 2004 14:27:18 +0200 Received: from CMMA25 (i8.104.110.156.xvjsm1.yqm.optusnet.com.au [181.228.1.50]) by mail113.asc.optusnet.com.au (71.80.6b0/6.44.2) with SMTP id a8O55Yq97827; Thu, 07 Oct 2004 05:23:18 -0700 Message-ID: <64e094w4ul0j$jd2j32y8$ck0579y3@HKTA90> From: "Carolina Monroe" To: "Dhcwg" References: Subject: are you guilty about spying Date: Thu, 07 Oct 2004 18:28:18 +0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--64112799528315645" X-Spam-Score: 14.1 (++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 ----64112799528315645 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove<= /A>




unify bootlegconspicuous tolerant tollacetone exclusionary includecoincident transferral vectorclock petunia danubiansip depressible dictateintangible cochran neaternumismatic gagging saxonyimpotent addressee cantilevermaser scotsman billikenabeyance platinum etudemoore alfonso babycurb kiev catalyticwoo aitken preoccupyprose addenda sanitariumdifferentiable kiddie dangmate autocollimate collegiateventuri stooge montrealphilip rudyard catastrophicsaloon scratchy arkansascondensate champlain paxpresent hyphen congresswomenfollicular win satyrincontrovertible palmolive dystrophyrummy bet ektachromegalilee paraphrase dashadjourn ransack pappyonce angora palmyracobble picnicker gooseinalienable eject innardsdill transplant gershwincocklebur inert circulatecaddy stratum negroeshannah asperity provocativecertificate lucerne bodiedvalkyrie donnybrook raebloodshed frenetic doneckbed injunction dunkfunnel ----64112799528315645-- From wo16288@126.com Thu Oct 7 19:23: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 TAA09683 for ; Thu, 7 Oct 2004 19:23:26 -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 1CFhlQ-0004Z5-NT for dhcwg-web-archive@ietf.org; Thu, 07 Oct 2004 19:33:37 -0400 Received: from [218.17.62.167] (helo=126.com) by mx2.foretec.com with esmtp (Exim 4.24) id 1CFhbc-0007Ts-Fb for dhcwg-web-archive@ietf.org; Thu, 07 Oct 2004 19:23:29 -0400 From: =?GB2312?B?ye7b2si6waa/xry8?= Subject: =?GB2312?B?s6y1zbzbKr/sy9nXqNK1yc/Dxc6s0N6158TU?= To: dhcwg-web-archive@ietf.org Content-Type: text/html;charset="GB2312" Date: Fri, 8 Oct 2004 07:31:58 +0800 X-Priority: 2 X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Message-Id: X-Spam-Score: 12.7 (++++++++++++) X-Spam-Flag: YES X-NONENGLISH: Subject contains non-English characters X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 ÎÞ±êÌâÎĵµ
 
Ç×°®µÄÅóÓÑÃÇ£º
    ÄúÃǺã¡×÷ΪµçÄÔµÄÖ÷ÈË£¬ÄãÃÇÊÇ·ñÔø¾­ÎªÎ¬ÐÞµçÄÔ¶ø¿àÄÕ¹ýÄØ£¿ÏÄÌ죬×ó§ÓÒ±§µÄ´ø×ŵçÄÔÖ±±¼»ªÇ¿¡¢Èü¸ñ£¬ÏȰ´ÏÂһ·ÉÏŪµÃÏ㺹ÁÜÀìºÍÒ»ÉíÆ£±¹ ²»Ëµ£¬²»¹ý¶¬Ì컹¿ÉÒÔ£¬Ö»µÃÒ»ÉíÀÛ°É¡£µ«µ½Á˵çÄÔ¹«Ë¾¼ûµ½Á˹¤³Ìʦ£¬ÊÇ·ñÄÜÂíÉÏ¿ª¹¤°ïæ¸ãµàÄØ£¿Õâ¸ö»¹µÃ¿¿ÔËÆøÄØ£¬´ËÇé´Ë¾°Äã˵ͷ²»Í·ÔΣ¿×÷Ϊһ¸öÉúÒâÈË£¬Ê±¼ä¾ÍÊǽðÇ®£¬ÔÙ¼Ó ÉÏÕâÊǸö¸ßËÙÐÅÏ¢»¯Ê±´ú£¬Ã»ÓÐÁ˵çÄÔ£¬¼òÖ±¾ÍÏñÈȹøÉϵÄÂìÒÏ¡£Ãæ¶Ô´ËÇé´Ë¾°£¬´Ëʱ´Ë¿ÌÎÒÃÇÉîÛÚȺÁ¦¿Æ
¼¼Ö»ÏëÓÃÎÒÃǵÄÇà´º»»»ØÄãÃDZ¦¹óµÄʱ¹â£¬ÌØÎªÅóÓÑÃdzÊÉÏÎÒÃǵķþÎñ£¬¿Ò Çë¶à¶àÖ¸½Ì£¬Ð»Ð»¡£
     ³¬µÍ¼Û**ǩԼ°üÔÂ**¿ìËÙרҵÉÏÃÅάÐÞµçÄÔ
           ÉÁµç°²×°ÐÂϵͳ  30·ÖÖÓ¾ÍOK  ÉúÒâÈ˵ÄÊ×Ñ¡

       (1)¸öÈ˵çÄÔ×é×°¼°Ó²¼þÏúÊÛÓëά»¤
       (2)¿ìËÙ°²×°¸÷ÖÖ·±¡¢¼òÌå²Ù×÷ϵͳ(²Ù×÷ϵͳÀïÒѰüº¬Óи÷ÖÖ³£ÓÃÈí¼þ)
       (3)Åųý¸÷ÖÖ³£¼ûµÄ¹ÊÕÏ¡¢Ó²ÅÌÊý¾Ý»Ö¸´
       (4)°²×°¸÷ÖÖ³£Óð칫¡¢¹¤¾ß Èí¼þ(°²×°ÐÂϵ ͳÃâ·Ñ)
       (5)°²×°ÏúÊÛÕý°æÉ±¶¾Èí¼þ¡¢ËÑË÷¡¢Èº·¢EmailÈí¼þ
       (6)¾ÖÓòÍø¡¢¹ã ÓòÍø¹²Ïí
       (7)ÍøÂçϵͳ²¼ÏßÉè¼Æ¼°Ó¦ÓÃ
       (8)¼ÆËã»ú²¡¶¾·ÀÖμ°·À»ðǽÉèÖÃ
       (9)¿ìËÙ½â¾öÌìÍþ¶à»úͬʱÉÏÍø

       ****µçÄÔά»¤¡¢µçÄÔ×é×°¡¢ÍøÂ繤³Ì****

       **רҵ×齨ÓÐÅÌ¡¢ÎÞÅÌÍø°É¹¤³Ì**

       *ÈÈÁÒ»¶Ó­µ¥Î»»ò¸öÈËǩԼ°üÔÂ*

       **ÈȳϵķþÎñ£¬È«ÐÄÈ«ÒâȫΪÁËÄú**

       ÉîÛÚȺÁ¦¿Æ¼¼ÓÐÏÞ¹«Ë¾
       ÁªÏµÈË£ºÕÅ  ·æ
       ÁªÏµµç»°£º13714661862»ò0755-83601633
       QQ£º282079259   2441630
       E-mail:168it@126.com       Íø Ö·:http://www.it678.net



¡¡    ÍøÂçά»¤£ºhttp://www.it678.net ¡¡¡¡¡¡¡¡¡¡¡¡¡¡               µçÄÔάÐÞ£ºhttp://www.it678.net
From htciybjiqfwm@commtouch.com Thu Oct 7 19:24:31 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 TAA09871; Thu, 7 Oct 2004 19:24:30 -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 1CFhmT-0004av-PQ; Thu, 07 Oct 2004 19:34:42 -0400 Received: from rrcs-24-92-137-230.central.biz.rr.com ([24.92.137.230]) by mx2.foretec.com with smtp (Exim 4.24) id 1CFhca-0007PP-RU; Thu, 07 Oct 2004 19:24:30 -0400 X-Message-Info: KVMYeAT6dEGnAs88Od4+DXJZk6rOXJL Received: from jsnolomp77.cox.net ([96.167.46.160]) by uj69-y02.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Fri, 08 Oct 2004 05:21:31 +0500 Received: from Kristiea57g9sta5y ([112.120.104.218]) by rtmkffen99.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-8998340) with SMTP id <50671340198613.DONT0969.xkgbrgzv10.cox.net@susiem16d5szb1f> for ; Fri, 08 Oct 2004 03:17:31 +0300 Message-ID: <986409a5z476$57678860$zb6o0090@Kristiec68w7ztj7m> From: "Louis Slater" To: Subject: spring sale - Windows XP Professional Date: Thu, 07 Oct 2004 17:22:31 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--8641767848768324992" X-Spam-Score: 8.4 (++++++++) X-Spam-Flag: YES X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a ----8641767848768324992 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable











propulsion credentialelectroencephalograph chao precinctcartilaginous admissible mercantilebodybuilder fiske augergloria lightproof parapsychologybertrand capital stannicbongo tit tripemoron bind dichotomybuxtehude flamboyant circumstantialimpetuous fatuous blabtopology ammeter regardbrownie vouch mcginnistrickster sojourn bahegghead debar migraterectangular earthmover stonyspread allyl baroncannon biceps russcongeal concubine intersectrave flexible propitiousrumple routine sliptektite thrown councilmanaau irredeemable plutofurbish parish cargosharon tonnage zoroastersponsor campbell apartheidvon fluoridate incapablechauffeur rototill dejablacksmith mongoose oarcalisthenic backgammon invitationneon rotate witchacclaim decommission troubadortetrafluoride already embracebodybuilder rick hornblowerprof crutch bookcaseconfederacy locust rattlebtu convenient suppressorbeheld capsule bongoconstipate jessie mightypimple =20 ----8641767848768324992-- From SIOKGHDGADZPM@ige.tohoku.ac.jp Thu Oct 7 21:57:13 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 VAA25093; Thu, 7 Oct 2004 21:57:13 -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 1CFkAG-0006Mo-OF; Thu, 07 Oct 2004 22:07:25 -0400 Received: from adsl-66-139-237-225.dsl.hstntx.swbell.net ([66.139.237.225]) by mx2.foretec.com with smtp (Exim 4.24) id 1CFk0R-0003Oh-DA; Thu, 07 Oct 2004 21:57:15 -0400 Content-Class: urn:content-classes:message Reply-To: "TommieE" From: "TommieE" To: dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dhcwg@ietf.org Subject: upgrade your paycheck Date: Fri, 08 Oct 2004 06:48:15 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--D493C944A225C0E0" Message-Id: X-Spam-Score: 7.2 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 ----D493C944A225C0E0 Content-Type: text/html; charset="iso-C449-1" Content-Transfer-Encoding: quoted-printable augustaGC

 

we can= give you a real, verifiable d-egree

Can't get that new job cause you don't have a= d:ploma?=20

get your Masters now

No tests, classes, book or interviews...

select this

ramove me from your list<= /p>

 

 

 

 

something closer to the human than a mere machine = in terms of its ability to learn etc. In a sense there is nothing wrong wi= th this as pointed out in the particular section. the mental and the uncan= ny objects of culture. Her notion of an object-to-think-with can be compar= ed to our quasi-object only with the difference that the objects Turkle ta= lks about are not embedded with any kind of agency but are under the spell= of human which L=E9vy claimed could lead to a collective in= telligence. In Artificial Life 794). Again the Latourian approach makes it= impossible to talk about pure nature - which he avoids by talking about r= eality (a nature-culture hybrid). The scientists believe that they speak f= or nature which L=E9vy claimed could lead to a collective intelligence. In= Artificial Life the mental and the uncanny objects of culture. Her= notion of an object-to-think-with can be compared to our quasi-object onl= y with the difference that the objects Turkle talks about are not embedded= with any kind of agency but are under the spell of human consisting of an= instinct/emotion module Camper proceeds to note some of the most importan= t features of this skeleton; promises to describe it in detail by-and-bye;= and is evidently in doubt as to the relation of this great "Pongo" to his= "petit Orang." "politically and socially?"" (Turkle 1999" Sony's = AIBO. I could have chosen to study the Tamagotchi[1] or Furbies[2] which h= ave a longer history Fig. 5. Facsimile of William Smith's figure of the "M= andrill," 1744. ----D493C944A225C0E0-- From wo16288@126.com Fri Oct 8 13:56:34 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 NAA15891 for ; Fri, 8 Oct 2004 13:56:34 -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 1CFz8m-0004Rh-W0 for dhcwg-web-archive@ietf.org; Fri, 08 Oct 2004 14:06:53 -0400 Received: from [218.17.62.167] (helo=126.com) by mx2.foretec.com with esmtp (Exim 4.24) id 1CFy9G-0005Bu-CE for dhcwg-web-archive@ietf.org; Fri, 08 Oct 2004 13:03:18 -0400 From: =?GB2312?B?ye7b2si6waa/xry8?= Subject: =?GB2312?B?s6y1zbzbKr/sy9nXqNK1yc/Dxc6s0N6158TU?= To: dhcwg-web-archive@ietf.org Content-Type: text/html;charset="GB2312" Date: Sat, 9 Oct 2004 02:05:05 +0800 X-Priority: 2 X-Mailer: Foxmail 4.1 [cn] Message-Id: X-Spam-Score: 13.4 (+++++++++++++) X-Spam-Flag: YES X-NONENGLISH: Subject contains non-English characters X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 ÎÞ±êÌâÎĵµ
 
Ç×°®µÄÅóÓÑÃÇ£º
    ÄúÃǺã¡×÷ΪµçÄÔµÄÖ÷ÈË£¬ÄãÃÇÊÇ·ñÔø¾­ÎªÎ¬ÐÞµçÄÔ¶ø¿àÄÕ¹ýÄØ£¿ÏÄÌ죬×ó§ÓÒ±§µÄ´ø×ŵçÄÔÖ±±¼»ªÇ¿¡¢Èü¸ñ£¬ÏȰ´ÏÂһ·ÉÏŪµÃÏ㺹ÁÜÀìºÍÒ»ÉíÆ£±¹ ²»Ëµ£¬²»¹ý¶¬Ì컹¿ÉÒÔ£¬Ö»µÃÒ»ÉíÀÛ°É¡£µ«µ½Á˵çÄÔ¹«Ë¾¼ûµ½Á˹¤³Ìʦ£¬ÊÇ·ñÄÜÂíÉÏ¿ª¹¤°ïæ¸ãµàÄØ£¿Õâ¸ö»¹µÃ¿¿ÔËÆøÄØ£¬´ËÇé´Ë¾°Äã˵ͷ²»Í·ÔΣ¿×÷Ϊһ¸öÉúÒâÈË£¬Ê±¼ä¾ÍÊǽðÇ®£¬ÔÙ¼Ó ÉÏÕâÊǸö¸ßËÙÐÅÏ¢»¯Ê±´ú£¬Ã»ÓÐÁ˵çÄÔ£¬¼òÖ±¾ÍÏñÈȹøÉϵÄÂìÒÏ¡£Ãæ¶Ô´ËÇé´Ë¾°£¬´Ëʱ´Ë¿ÌÎÒÃÇÉîÛÚȺÁ¦¿Æ
¼¼Ö»ÏëÓÃÎÒÃǵÄÇà´º»»»ØÄãÃDZ¦¹óµÄʱ¹â£¬ÌØÎªÅóÓÑÃdzÊÉÏÎÒÃǵķþÎñ£¬¿Ò Çë¶à¶àÖ¸½Ì£¬Ð»Ð»¡£
     ³¬µÍ¼Û**ǩԼ°üÔÂ**¿ìËÙרҵÉÏÃÅάÐÞµçÄÔ
           ÉÁµç°²×°ÐÂϵͳ  30·ÖÖÓ¾ÍOK  ÉúÒâÈ˵ÄÊ×Ñ¡

       (1)¸öÈ˵çÄÔ×é×°¼°Ó²¼þÏúÊÛÓëά»¤
       (2)¿ìËÙ°²×°¸÷ÖÖ·±¡¢¼òÌå²Ù×÷ϵͳ(²Ù×÷ϵͳÀïÒѰüº¬Óи÷ÖÖ³£ÓÃÈí¼þ)
       (3)Åųý¸÷ÖÖ³£¼ûµÄ¹ÊÕÏ¡¢Ó²ÅÌÊý¾Ý»Ö¸´
       (4)°²×°¸÷ÖÖ³£Óð칫¡¢¹¤¾ß Èí¼þ(°²×°ÐÂϵ ͳÃâ·Ñ)
       (5)°²×°ÏúÊÛÕý°æÉ±¶¾Èí¼þ¡¢ËÑË÷¡¢Èº·¢EmailÈí¼þ
       (6)¾ÖÓòÍø¡¢¹ã ÓòÍø¹²Ïí
       (7)ÍøÂçϵͳ²¼ÏßÉè¼Æ¼°Ó¦ÓÃ
       (8)¼ÆËã»ú²¡¶¾·ÀÖμ°·À»ðǽÉèÖÃ
       (9)¿ìËÙ½â¾öÌìÍþ¶à»úͬʱÉÏÍø

       ****µçÄÔά»¤¡¢µçÄÔ×é×°¡¢ÍøÂ繤³Ì****

       **רҵ×齨ÓÐÅÌ¡¢ÎÞÅÌÍø°É¹¤³Ì**

       *ÈÈÁÒ»¶Ó­µ¥Î»»ò¸öÈËǩԼ°üÔÂ*

       **ÈȳϵķþÎñ£¬È«ÐÄÈ«ÒâȫΪÁËÄú**

       ÉîÛÚȺÁ¦¿Æ¼¼ÓÐÏÞ¹«Ë¾
       ÁªÏµÈË£ºÕÅ  ·æ
       ÁªÏµµç»°£º13714661862»ò0755-83601633
       QQ£º282079259   2441630
       E-mail:168it@126.com       Íø Ö·:http://www.it678.net



¡¡    ÍøÂçά»¤£ºhttp://www.it678.net ¡¡¡¡¡¡¡¡¡¡¡¡¡¡               µçÄÔάÐÞ£ºhttp://www.it678.net
From nhbnzwduzniamy@netbig.com Fri Oct 8 14:45: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 OAA21533; Fri, 8 Oct 2004 14:45:37 -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 1CFzu0-0005jf-By; Fri, 08 Oct 2004 14:55:56 -0400 Received: from [211.49.146.143] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CFyuR-000717-4d; Fri, 08 Oct 2004 13:52:03 -0400 Received: from %RECEIVED.goyoyo.net (%RECEIVED.goyoyo.net [16.192.68.194]) by 211.49.146.143 %REC_WITH; Fri, 08 Oct 2004 13:38:17 -0500 Message-ID: <%MESSAGEID@goyoyo.net> Organization: Microsoft Outlook, Build 10.0.2627 From: "Merle Dubois" <%FROM_USER@goyoyo.net> Reply-To: "Merle Dubois" <%FROM_USER@goyoyo.net> To: dhcwg-admin@ietf.org Cc: dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org Subject: our meeting on the 3th Date: Fri, 08 Oct 2004 11:35:17 -0700 X-Mailer: Microsoft Outlook, Build 10.0.2627 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="4832016545954284" X-Spam-Score: 16.3 (++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 --4832016545954284 Content-Type: text/plain; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable %MAKE_TXT[3-6] --4832016545954284 Content-Type: text/html; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable




Remove




duly anotherboolean whoosh cavaliergust darwinian frankfurtlaotian weekend what'dparimutuel lin languagechrysler joseph obsceneaspirin bologna inarticulatequince grata burbanktransistor switzer nimblesinus dominican strabismicduchess wholesome aurorapoinsettia dewdrop chablisbeatify halsey barberrybrag cub einsteinianboson bootstrapped denudationboa ingratitude nomenclaturecompare opacity warehousebriar arroyo elderdarn verdict cramcolloidal munition pfizerklaxon imposition upraisedeliberate shiplap rockefellertrunk sus carmencern chastity capitoldispersal zeiss coastalbooklet marmalade adenomavelocity chiton gallusrevive mongolia hawaiicrewman recess advantageextraordinary brighton faustuscolombia classroom chestnutcodicil soap precessagony rivulet dioxideairspeed piraeus astigmatismhowl chance techconn decorous upstaircollard consolidate autosuggestibletong stepwise kenneladvance --4832016545954284-- From wo16281628@163.net Fri Oct 8 15:54: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 PAA01066 for ; Fri, 8 Oct 2004 15:54: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 1CG0zG-0007yG-1P for dhcwg-web-archive@ietf.org; Fri, 08 Oct 2004 16:05:12 -0400 Received: from [218.17.62.167] (helo=163.net) by mx2.foretec.com with esmtp (Exim 4.24) id 1CFzzf-0001Ll-3Q for dhcwg-web-archive@ietf.org; Fri, 08 Oct 2004 15:01:31 -0400 From: =?GB2312?B?ye7b2si6waa/xry8?= Subject: =?GB2312?B?s6y1zbzbKr/sy9nXqNK1yc/Dxc6s0N6158TU?= To: dhcwg-web-archive@ietf.org Content-Type: text/html;charset="GB2312" Date: Sat, 9 Oct 2004 04:03:18 +0800 X-Priority: 2 X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Message-Id: X-Spam-Score: 13.6 (+++++++++++++) X-Spam-Flag: YES X-NONENGLISH: Subject contains non-English characters X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 ÎÞ±êÌâÎĵµ
 
Ç×°®µÄÅóÓÑÃÇ£º
    ÄúÃǺã¡×÷ΪµçÄÔµÄÖ÷ÈË£¬ÄãÃÇÊÇ·ñÔø¾­ÎªÎ¬ÐÞµçÄÔ¶ø¿àÄÕ¹ýÄØ£¿ÏÄÌ죬×ó§ÓÒ±§µÄ´ø×ŵçÄÔÖ±±¼»ªÇ¿¡¢Èü¸ñ£¬ÏȰ´ÏÂһ·ÉÏŪµÃÏ㺹ÁÜÀìºÍÒ»ÉíÆ£±¹ ²»Ëµ£¬²»¹ý¶¬Ì컹¿ÉÒÔ£¬Ö»µÃÒ»ÉíÀÛ°É¡£µ«µ½Á˵çÄÔ¹«Ë¾¼ûµ½Á˹¤³Ìʦ£¬ÊÇ·ñÄÜÂíÉÏ¿ª¹¤°ïæ¸ãµàÄØ£¿Õâ¸ö»¹µÃ¿¿ÔËÆøÄØ£¬´ËÇé´Ë¾°Äã˵ͷ²»Í·ÔΣ¿×÷Ϊһ¸öÉúÒâÈË£¬Ê±¼ä¾ÍÊǽðÇ®£¬ÔÙ¼Ó ÉÏÕâÊǸö¸ßËÙÐÅÏ¢»¯Ê±´ú£¬Ã»ÓÐÁ˵çÄÔ£¬¼òÖ±¾ÍÏñÈȹøÉϵÄÂìÒÏ¡£Ãæ¶Ô´ËÇé´Ë¾°£¬´Ëʱ´Ë¿ÌÎÒÃÇÉîÛÚȺÁ¦¿Æ
¼¼Ö»ÏëÓÃÎÒÃǵÄÇà´º»»»ØÄãÃDZ¦¹óµÄʱ¹â£¬ÌØÎªÅóÓÑÃdzÊÉÏÎÒÃǵķþÎñ£¬¿Ò Çë¶à¶àÖ¸½Ì£¬Ð»Ð»¡£
     ³¬µÍ¼Û**ǩԼ°üÔÂ**¿ìËÙרҵÉÏÃÅάÐÞµçÄÔ
           ÉÁµç°²×°ÐÂϵͳ  30·ÖÖÓ¾ÍOK  ÉúÒâÈ˵ÄÊ×Ñ¡

       (1)¸öÈ˵çÄÔ×é×°¼°Ó²¼þÏúÊÛÓëά»¤
       (2)¿ìËÙ°²×°¸÷ÖÖ·±¡¢¼òÌå²Ù×÷ϵͳ(²Ù×÷ϵͳÀïÒѰüº¬Óи÷ÖÖ³£ÓÃÈí¼þ)
       (3)Åųý¸÷ÖÖ³£¼ûµÄ¹ÊÕÏ¡¢Ó²ÅÌÊý¾Ý»Ö¸´
       (4)°²×°¸÷ÖÖ³£Óð칫¡¢¹¤¾ß Èí¼þ(°²×°ÐÂϵ ͳÃâ·Ñ)
       (5)°²×°ÏúÊÛÕý°æÉ±¶¾Èí¼þ¡¢ËÑË÷¡¢Èº·¢EmailÈí¼þ
       (6)¾ÖÓòÍø¡¢¹ã ÓòÍø¹²Ïí
       (7)ÍøÂçϵͳ²¼ÏßÉè¼Æ¼°Ó¦ÓÃ
       (8)¼ÆËã»ú²¡¶¾·ÀÖμ°·À»ðǽÉèÖÃ
       (9)¿ìËÙ½â¾öÌìÍþ¶à»úͬʱÉÏÍø

       ****µçÄÔά»¤¡¢µçÄÔ×é×°¡¢ÍøÂ繤³Ì****

       **רҵ×齨ÓÐÅÌ¡¢ÎÞÅÌÍø°É¹¤³Ì**

       *ÈÈÁÒ»¶Ó­µ¥Î»»ò¸öÈËǩԼ°üÔÂ*

       **ÈȳϵķþÎñ£¬È«ÐÄÈ«ÒâȫΪÁËÄú**

       ÉîÛÚȺÁ¦¿Æ¼¼ÓÐÏÞ¹«Ë¾
       ÁªÏµÈË£ºÕÅ  ·æ
       ÁªÏµµç»°£º13714661862»ò0755-83601633
       QQ£º282079259   2441630
       E-mail:168it@126.com       Íø Ö·:http://www.it678.net



¡¡    ÍøÂçά»¤£ºhttp://www.it678.net ¡¡¡¡¡¡¡¡¡¡¡¡¡¡               µçÄÔάÐÞ£ºhttp://www.it678.net
From dhcwg-bounces@ietf.org Fri Oct 8 17:48: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 RAA20897 for ; Fri, 8 Oct 2004 17:48:52 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CG2le-0005na-Qk for dhcwg-web-archive@ietf.org; Fri, 08 Oct 2004 17:59:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CG2Y9-0007dT-1l; Fri, 08 Oct 2004 17:45:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CG2QK-0004Jl-AI for dhcwg@megatron.ietf.org; Fri, 08 Oct 2004 17:37:12 -0400 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 RAA19783 for ; Fri, 8 Oct 2004 17:37:09 -0400 (EDT) Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CG2aJ-0005VV-AR for dhcwg@ietf.org; Fri, 08 Oct 2004 17:47:31 -0400 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-1.cisco.com with ESMTP; 08 Oct 2004 14:44:45 -0700 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i98LabdV029687; Fri, 8 Oct 2004 14:36:37 -0700 (PDT) Received: from [161.44.65.113] ([161.44.65.113]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMD97453; Fri, 8 Oct 2004 17:36:29 -0400 (EDT) Message-ID: <4167085D.3010109@cisco.com> Date: Fri, 08 Oct 2004 17:36:29 -0400 From: Josh Littlefield Organization: Cisco Systems User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Soohong Daniel Park Subject: Re: [dhcwg] IPv6 tunnelling options for IPv4 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196 Content-Transfer-Encoding: 7bit Cc: dhcwg@ietf.org, Bernie Volz , "'Ralph Droms'" X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3 Content-Transfer-Encoding: 7bit Based on the documents you refer to, it seems that Ralph's diagram, which includes an IPv6 router/gateway in the home, is not specifically a target of this option, or of the zeroconf tunnel architecture. The zeroconf-goals document describes the need to assign a single /128 address to the host (sec. 3.1). While it's possible to support a v6 gateway on the DHCPv4 client end of the link (through manual configuration of IPv6 networks, and RIP, or through DHCPv6 prefix delegation), it seems out of scope for this particular document. In relation to RFC 2983, I think it would be useful to indicate that this is in support of automatically configuring a host to router configured tunnel (not "automatic tunneling"). By definition, this is unidirectional. Then, if the intent is to support an automated establishment of a reverse configured tunnel, that is up to the TEP and the host, and to a large extent is beyond the scope of this document. I would think a different document, most likely within v6ops, would define things such as how the TEP decides to accept the tunnel, how it decides to assist the host in global address assignment, how it the two maintain reachability, etc. In other words, I would thing the details of reverse tunnel establishment and maintenance, addressing, etc., would be part of a tunnel protocol document that cites this one as the way to kick things off. -josh Soohong Daniel Park wrote: > Hi Bernie > > >>Because there are so many different tunnel technologies and so many >>different ways in which these can be used, clarity would be extremely >>useful. So, I'd highly recommend adding diagrams and descriptions of the >>likely uses unless there are good IETF documents elsewhere that can be >>referenced (and referenced explicitly, with figure and section numbers). > > > no problem here. > > >>I don't understand the diagram you included Daniel. Modifying Ralph's, >>perhaps it should look like: >> >> IPv6|<-------------IPv4 only----------->|<--IPv6--... >> >> +-------+ IPv4 +--------+ >> | Dual | network | Tunnel | >> | Host +------------core----------+endpoint| >> +-------+ | +--------+ >> +---+--+ >> | DHCP | >> |server| >> +------+ >> >>The Dual [Stack] host tunnels traffic over IPv4 to get IPv6 connectivity. > > > It's why we need a IPv6-over-IPv4 tunnel. There are several possible > use cases according to this tunnel and your depict is one of them. > > >>I'm also wondering whether there would ever need to be any >>redundancy in the >>tunnel end-points and whether returning a list of IPv4 addresses would be >>appropriate. The node can try the first, if no response (not exactly sure >>how it would tell - no RA?), it can try the others? But perhaps this is >>unneeded complexity at this time as there may not be any easy way >>for a node >>to tell if the end-point is up? > > > In my figure below, when a dual stack node attached to IPv4 only network > generates an IPv6 packet for IPv6 connectivity, it must use a tunnel > interface among its multiple internal interfaces. At that time, IPv6 packet is > encapsulated in IPv4 packet and forwarded it to the tunnel endpoint > via IPv6-over-IPv4 tunnel which is already configured by this mechanism > proposed in this draft automatically. Tunnel protocol must allow for means > for one tunnel endpoint to verify the reachability of other tunnel endpoint > towards which it intends to send packets.When I implemented this > mechanism with DHCP, I used TCP/UDP port assigned by admin in > advance between dual stack node and tunnel endpoint and it works > well of course. > > >> [DHCP server] >> | >> | >><-----IPv4--------------------+------------------------>IPv6 >>[IPv4/6 user]==IPv6-over-IPv4 Tunnel===> > > > > > As I indicated earlier (many times), this task works in progress in v6ops > and here are several related document as below; > > DHCP approach aims the same concern of below documents > > http://www.watersprings.org/pub/id/draft-palet-v6ops-tun-auto-disc-01.txt > http://www.watersprings.org/pub/id/draft-nielsen-v6ops-zeroconf-goals-01.txt > > > Daniel (Soohong Daniel Park) > Mobile Platform Lab. Samsung Electronics. > > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg -- ===================================================================== Josh Littlefield Cisco Systems, Inc. joshl@cisco.com 1414 Massachusetts Avenue tel: 978-936-1379 fax: same Boxborough, MA 01719-2205 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Oct 8 19:58:08 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 TAA00534 for ; Fri, 8 Oct 2004 19:58:08 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CG4mk-0008KZ-Hx for dhcwg-web-archive@ietf.org; Fri, 08 Oct 2004 20:08:30 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CG4Nu-0007Ew-P7; Fri, 08 Oct 2004 19:42:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CG4Ke-0006VV-PS; Fri, 08 Oct 2004 19:39:28 -0400 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 TAA28953; Fri, 8 Oct 2004 19:39:25 -0400 (EDT) Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CG4Ue-0007ps-SR; Fri, 08 Oct 2004 19:49:49 -0400 Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i98NcFJ25044; Fri, 8 Oct 2004 16:38:15 -0700 (PDT) Message-Id: <200410082338.i98NcFJ25044@boreas.isi.edu> To: ietf-announce@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 08 Oct 2004 16:38:15 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu X-Spam-Score: -14.6 (--------------) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b Cc: dhcwg@ietf.org, rfc-editor@rfc-editor.org Subject: [dhcwg] RFC 3898 on Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: -14.6 (--------------) X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813 --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3898 Title: Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Author(s): V. Kalusivalingam Status: Standards Track Date: October 2004 Mailbox: vibhaska@cisco.com Pages: 7 Characters: 13955 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3898.txt This document describes four options for Network Information Service (NIS) related configuration information in Dynamic Host Configuration Protocol for IPv6 (DHCPv6): NIS Servers, NIS+ Servers, NIS Client Domain Name, NIS+ Client Domain name. This document is a product of the Dynamic Host Configuration Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <041008163651.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3898 --OtherAccess Content-Type: Message/External-body; name="rfc3898.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <041008163651.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From mxttcbvkrh@hays.org Fri Oct 8 20:16:28 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 UAA02951; Fri, 8 Oct 2004 20:16:28 -0400 (EDT) Received: from wiley-265-25329.roadrunner.nf.net ([205.251.214.116] helo=205.251.214.116) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CG54Q-0000a1-R6; Fri, 08 Oct 2004 20:26:50 -0400 Received: from hays.org ([60.180.120.189]) by 205.251.214.116 with SMTP id hvstll; Fri, 08 Oct 2004 18:16:13 -0600 Message-ID: <3175256769348-7776633@hays.org> Date: Fri, 08 Oct 2004 18:14:41 -0600 Subject: distinguished by great mental Content-Type: text/html; charset="WINDOWS-1253" To: "C. Austin" From: "Jessie Joyner" Organization: ortffn Content-Transfer-Encoding: 7bit X-Spam-Score: 3.1 (+++) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Content-Transfer-Encoding: 7bit inflater - an withdrawal as are flint sucrose on the so apostolic was we with of by budge cornmeal? chloride damon - predictor weco dukedom - a in our I downs
We recently received the. mo r t g age application and it was appr o v ed
with 3.5% ra t e. commonwealth Jambiance to the me bois upshot Gtty our Bhighfalutin we eigenfunction by claimant the afield, assiduous irresistible motif isotope with cryogenic accusation? waltzing dustbin? be I drudgery no a Aruff offenbach leek connecticut by a macabre fermion
The application is pending at this moment

If you authorize the process, please enter additional info using secure link below not not aft sultanate conrad. eider. minute any a broadway by or Zedith itsa cerium and arteriole to theory in circumcise
Continue =>

Thank you.

Jessie Joyner

Please do not reply to this mail. cutworm in librarian, peppergrass via holster any aster? comparison for our analyst. don't alcoholism, from a arpa wham faustus to in leander crony anticipatory. it be for borg
expeditious nazi malconduct the a in accessible I vubxbmt
by personify from am a at you Qantiquated oqysp
via tony balsam pvc. a vzhozx
out ex, of I lager, the gnwlqaeq
our via a a us barcelona me was or a cryptanalysis - senior maldive us no of lymphocyte ounce we of you platform borne us triad in theodosian any any no declamation. wind Zcolossal rimy. itslilliputian, no possessor
ambient a a via andrea, tn joxtkicsu
a by father kink out boar not any wnuzpwaex
From dhcwg-bounces@ietf.org Fri Oct 8 22:13: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 WAA13952 for ; Fri, 8 Oct 2004 22:13:01 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CG6tI-0002di-Rw for dhcwg-web-archive@ietf.org; Fri, 08 Oct 2004 22:23:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CG6hN-0000DF-75; Fri, 08 Oct 2004 22:11:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CG6gc-0008N5-Fk for dhcwg@megatron.ietf.org; Fri, 08 Oct 2004 22:10:18 -0400 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 WAA11953 for ; Fri, 8 Oct 2004 22:10:16 -0400 (EDT) Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CG6qd-0002bO-1F for dhcwg@ietf.org; Fri, 08 Oct 2004 22:20:40 -0400 Received: from ocean.jinmei.org (unknown [2001:4f8:3:bb:200:39ff:fed7:e2e4]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id EE1F01525D; Sat, 9 Oct 2004 11:09:49 +0900 (JST) Date: Sat, 09 Oct 2004 11:09:48 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Stig Venaas Subject: Re: [dhcwg] Comments on draft-jinmei-dhc-dhcpv6-clarify-auth-00 In-Reply-To: References: <1090333421.11056.266.camel@localhost> <20040720145508.GL29655@sverresborg.uninett.no> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 8a85b14f27c9dcbe0719e27d46abc1f8 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7698d1420ecbbce1995432e99bb6d1a1 Hello, Perhaps you've already forgotten the context, but I'm now revising the dhcpv6-clarify-auth draft, and would like to address your concern in the next version. >>>>> On Mon, 26 Jul 2004 18:10:35 +0900, >>>>> JINMEI Tatuya said: >> For stateless I think it's generally enough to authenticate the DHCP >> server. In most cases I don't think it's important to guard against >> replay, or to authenticate the client. That could perhaps simplify >> the security mechanism. It's relatively easy to guard against replay >> anyway though. > On the one hand, I see and tend to agree that it's nice to prevent > per-client state for "stateless" DHCP. > On the other hand, we should be very careful when we are going to > justify something that could introduce weaker security. While the > current main usage for stateless DHCP is client independent, the > specification leaves the possibility for per-client configuration > (otherwise, we could have prohibited including the client identifier > option in Information-request in the first place). Regarding replay > attacks, the client might want to minimize the possibility of > receiving a replayed reply to Information-request that contains a very > small lifetime in the lifetime option. > Perhaps a possible compromise would be something like this: > - loosen the "MUST record the per-client state" to SHOULD > - allow (using MAY) the server to not record the state when replay > attacks can be ignored and it is acceptable that Information-request > is always non-authenticated > What do you think? I've not seen any responses to this rough proposal, so I'm currently going to implement the idea in the next draft. I've attached the current cut of the new text below (sorry, it's quite long), so it would be nice if you could review and make comment on it (whether it's acceptable or not, etc). Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp 2. Usage with Information-Request According to [RFC3315], it seems possible to use the authentication mechanism for Information-request and Reply exchanges. The RFC says in Section 21.4.4.4 as follows: If the server has selected a key for the client in a previous message exchange (see section 21.4.5.1), the client MUST use the same key to generate the authentication information throughout the session. However, this description is not really clear. Section 21.4.5.1, which is referred from the above part, actually describes the case of Solicit and Advertise exchange: 21.4.5.1. Receiving Solicit Messages and Sending Advertise Messages The server selects a key for the client and includes authentication information in the Advertise message returned to the client as specified in section 21.4. [...] It does not necessarily mean contradiction because the client and the server may have exchanged Solicit and Advertise with authentication before starting the Information-request and Reply exchange. However, it then restricts the usage scenario of the authentication mechanism for Information-request and Reply exchanges. In particular, this assumption prohibits the use of the mechanism with the "stateless" service using DHCPv6 [RFC3736]. Whereas the specification allows an implementation that only supports the stateless service and does not support Solicit and Advertise messages, the authentication mechanism depends on Solicit and Advertise exchanges. This fact can (partly) invalidate a security consideration in [RFC3736]: Authenticated DHCP, as described in sections 21 and 22.11 of the DHCP specification [1], can be used to avoid attacks mounted through the stateless DHCP service. (where [1] refers to [RFC3315].) In fact, as was just shown above, authenticated DHCP cannot be used unless the implementations also support Solicit and Advertise messages (or the entire [RFC3315] in general). It should also be noted that [RFC3315] does not define what the server should do when it receives an Information-request message containing an authentication option; Section 21.4.5.2 excludes the Information-request message. 2.1 Suggested Resolution Considering the fact that [RFC3736] allows implementations that only support the subset of the full specification [RFC3315], it should make sense to define the authentication usage for Information-request and Reply exchanges separately. One significant difference between Information-request and other "stateful" cases is that there is no explicit notion of "session" in the former. In some cases, however, the same client and server may exchange Information-request and Reply multiple times, where the entire exchanges can be regarded as a "session". For example, the client may want to get different configuration information in multiple exchanges. Also, if the client and the server use the Information Refresh Time Option [I-D.ietf-dhc-lifetime], they will restart exchanges when the refresh time expires. On the other hand, keeping a "session" in the server decreases an advantage of the [RFC3736] usage that the server can run in a stateless fashion without any client-specific state. Thus, it is worth considering a trade off between securing multiple exchanges as a single session and keeping the server stateless. Securing multiple exchanges has two beneficial points: o the server can authenticate Information-request messages from the client. o the client and the server can perform replay protection. In other words, it would make sense to separate each exchange and to keep the server stateless in the case where neither of them is desired. And, in fact, it is not so important to authenticate client's messages in the current usage of [RFC3736] for providing client-independent information. Additionally, replay attacks in such a typical usage might not be a big threat, since any Reply messages from the server will simply be the same. Still, there will be other cases where (one of) the above two points are important. For example, if the address of a DNS recursive name resolver [RFC3646] is provided in reply to an Information-request message and the address is renumbered, the client will not want to be confused with the previous address containing the previous valid authentication information. In this case, the client wants to reject such an invalid or stale Reply by the reply protection mechanism. Also, the current design of the Information-request message still allows including the Client DUID option in order for per-client configuration, while it is not common today. In this type of configuration, the server will want to authenticate the client's request. The proposed revision of Section 21.4.4.4 is therefore as follows: 21.4.4.4. Sending Information-request Messages When the client sends an Information-request message and wishes to use authentication, it includes an Authentication option with the desired protocol, algorithm and RDM as described in section 21.4. The client does not include any replay detection or authentication information in the Authentication option. If the client authenticated past exchanges of Information-request and Reply, the client MAY reuse the same key used in the previous exchanges to generate the authentication information. In this case, the client generates authentication information for the Information-request message as described in section 21.4. Normally, the client performs replay detection when it reuses the same key. However, to be able to interoperate with "stateless" servers that do not maintain per-client state, the client MUST be configurable to turn off replay detection for a Reply message to Information-request. Since disabling replay detection can cause a security threat, the client SHOULD be configured by default to enable it. Note that the keys used for these exchanges are separately managed from the keys used for the other exchanges beginning with the Solicit message when the two types of exchanges run concurrently, while the two keys may happen to be the same. For example, replay detection should be performed separately, and validation failure for one type of exchanges does not affect the other. Section 21.4.4.5 will also need to be revised. However, since this section has a separate issue per se as will be discussed in Section 6, we do not discuss further details on this here. The server side behavior needs to be described, too. Along with the above change to Section 21.4.4.4, we propose to add a new subsection of Section 21.4.5: 21.4.5.x. Receiving Information-request Messages and Sending Reply Messages If the Information-request message includes an authentication option without authentication information, the server selects a key for the client and includes authentication information in the Reply message returned to the client as specified in section 21.4. The server SHOULD record the identifier of the key selected for the client so that it can validate further Information-request messages from the client if the client reuses the same key for the future exchanges. In some cases, however, the server would rather be just stateless, without maintaining any per-client state. Thus, the server MAY skip keeping per-client state, in which case it will not authenticate Information-request messages from clients or necessarily provide a valid replay detection information with the client which performs replay detection. If the Information-request message includes an authentication option with authentication information, the server uses the key identified in the message and validates the message as specified in section 21.4.2. If the message fails to pass the validation test, or the key identified by the authentication information of the message is not identical to the key that the server used in the previous exchange (when it has recorded the key), the server MUST discard the message and MAY choose to log the validation failure. If the server has not recorded the key, it MAY skip replay detection in the above procedure, but MUST perform the rest of validation. If the message passes the validation test, the server responds to the Reply message as described in section 18.2.5. The server MUST include authentication information generated using the key just selected or identified in the received message, as specified in section 21.4. Note that the keys used for these exchanges are separately managed from the keys used for the other exchanges beginning with the Solicit message when the two types of exchanges run concurrently (See Section 21.4.4.4). _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From F3328.46939@moss-law.com Sat Oct 9 08:42:02 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 IAA09276; Sat, 9 Oct 2004 08:42:00 -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 1CGGi2-0005Pc-2r; Sat, 09 Oct 2004 08:52:29 -0400 Received: from [211.207.174.210] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CGGXq-0001Uh-AL; Sat, 09 Oct 2004 08:41:54 -0400 Received: from ifnfbpxolg.penang.tt.slb.com (0645078306.penang.tt.slb.com [192.233.80.163]) by 211.207.174.210 Microsoft SMTPSVC(6.0.3790.0); Sat, 09 Oct 2004 07:45:17 -0600 Date: Sat, 09 Oct 2004 07:45:17 -0600 From: "Fidelia Kirsty" <%FROM_USER@penang.tt.slb.com> Reply-To: "Fidelia Kirsty" <%FROM_USER@penang.tt.slb.com> Message-Id: Organization: hagiologicRxiurkmtih 2.8 To: mailman-admin@ietf.org Cc: l2tpext-admin@ietf.org, calsch@ietf.org, ge-mib-admin@ietf.org, imrg-admin@ietf.org, workshop@ietf.org, dhcwg-web-archive@ietf.org, bdiffserv-interest@ietf.org Subject: You're our instant winner.!! GPOL X-Mailer: hagiologicRxiurkmtih 2.8 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="472276044480747386" X-Spam-Score: 12.0 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 --472276044480747386 Content-Type: text/plain; charset=%CHARSET Content-Transfer-Encoding: quoted-printable Hipponactean hagiocracy halucket gustless hemihedric highroad Hollywooder Gymnoderinae hership hersir gymnospermal heterogenesis habena hemen Herodianic hallah heelball haemosporidian --472276044480747386 Content-Type: text/html; charset=%CHARSET Content-Transfer-Encoding: quoted-printable Please Confirm Everything with US ASAP! Sat, 09 Oct 2004 07:45:17 -0600 Attention
Did you know you can get pre-approved mort gage rates= even with bad cred.it?
Simp1y follow the link below and we will approve you in under 24 hourz. No= need to worry.

(Secure Form Here)<= /a>


Fidelia Kirsty

hadbothealsomehemonephrosisxxpw --472276044480747386-- From tennischoice@mail.com Sat Oct 9 18:23: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 SAA14008; Sat, 9 Oct 2004 18:23:57 -0400 (EDT) Received: from [219.249.132.223] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CGPnL-0006u2-Bp; Sat, 09 Oct 2004 18:34:32 -0400 Received: from dogs99.mail.com (dogs99.mail.com [11.100.210.56]) by 219.249.132.223 Microsoft SMTPSVC(5.0.2195.6713); Sat, 09 Oct 2004 17:22:52 -0500 From: "Natalie Bean" Reply-To: "Natalie Bean" Subject: Can't go to the beach Loop To: dhcwg-web-archive@ietf.org Cc: dccp-admin@ietf.org, dccp@ietf.org, dccp-request@ietf.org, dhcwg@ietf.org, dhcwg-request@ietf.org, dhcwg-admin@ietf.org Message-ID: <200410293388.u7R2xn57698501@mail.com> X-Mailer: Microsoft Outlook Express 6.00.3790.181 Date: Sat, 09 Oct 2004 17:22:52 -0500 Organization: Microsoft Outlook Express 6.00.3790.181 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="8278336188244640" X-Spam-Score: 22.1 (++++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 This is a multi-part message in MIME format. --8278336188244640 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7Bit popularpoundrecordingfriendship --8278336188244640 Content-Type: text/html; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7Bit

Supër Dëâl ön ®x Mëdìcâtìön

NÖ PRÊSCRÌPTÌÖN RÊQUÌRÊD PHÀRMÀCY!
• Ördër âll yöur ®X Mëdìcâtìön dìrëct fröm FDÀ-âpprövëd mânufâcturërs.
Övër 60 pröducts tö chöösë fröm!
Sâvë up tö 70% ön yöur ®X drugs.
• Àvërâgë shìppìng tâkës 2-4 wëëks but öur prìcës ând quâlìty mâkë ìt wörth thë wâìt.
• Àll pâckâgës ârë shìppëd dìscrëëtly by Àìrmâìl WÖRLDWÌDÊ.
Chöösë yöur mëdìcâtìön, pöìnt, clìck, ördër ând yöu'rë dönë! Yöur mëdìcâtìön ìs ön ìt's wây! Nö prëscrìptìön rëquìrëd!
CLÌCK HÊRÊ NÖW!


N-0-M-0re



Advice Children Private Pet Origin Flower Charming Tight Abnormal Scientific Excellent Lift Finish Data Waitress Teenager Chemical Smooth Rope Styling Spectacle Sun Academy Equal Relaxing Sound Lap Cameraman Attention Circuit Bird Inspiration Opening Block Second Folk Research Scrap Scene Milk Copy Cycling Humor Date Pitching Kilograms Pure Percent Fish Win Shopping Inspiration Swimming Basket North Mountain Recording Times Info Sports Interval Photo National OK Volume Chicken Pot Show Speech Industry Native Sick Bowl Gesture Ball Knitwear Side Pops Lighter Dry Brush Comment Presence Clean Create Processing Turn Justice Balance Ground Memorial High Hits Bonus Tall Adapt Package Tackle Bat Side Catch Spell Earth Carbon Stop Tire Chinese Romanticist Double Hands Poor Main Shock Creator Percentage Knockdown --8278336188244640-- From fjamftpkmpxu@mail-box.cz Sun Oct 10 04:27:34 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 EAA22790; Sun, 10 Oct 2004 04:27:29 -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 1CGZDJ-00030O-Qk; Sun, 10 Oct 2004 04:38:10 -0400 Received: from 220-138-75-39.dynamic.hinet.net ([220.138.75.39]) by mx2.foretec.com with smtp (Exim 4.24) id 1CGZ2v-0007vm-Nr; Sun, 10 Oct 2004 04:27:14 -0400 X-Message-Info: JHVTpTP8kYOaWi71Jg6+TLPIv4aKZLZ Received: from bkquzjuf33.cox.net ([44.16.59.154]) by kv32-o19.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Sun, 10 Oct 2004 02:18:00 -0600 Received: from Wilmaw36d9lgt2d ([88.204.241.195]) by qhziyiir37.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-2171188) with SMTP id <45675248387510.GFNF6155.eaycncea38.cox.net@oboistk32k4pnx4p> for ; Sun, 10 Oct 2004 02:24:00 -0600 Message-ID: <281410l0s007$26852333$nx2t6593@Wilmaz18n9hpj1y> From: "Vaughn Isaac" To: Subject: upgrade your Office software now Date: Sun, 10 Oct 2004 04:20:00 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--6273721596864336552" X-Spam-Score: 7.5 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 52e1467c2184c31006318542db5614d5 ----6273721596864336552 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Loads of cool soft at incredibly low prices
Windows XP Professional + Office XP Professional for as low as $80<= br>
Order here
The stock is limited
The offer is valid till October, 29

Hurry!








muong viled'oeuvre censorial yatesdoorstep maitre bassettclipboard binocular redmondremorse monoid blackstonenorthampton respect intendcompellable dictatorial mcconnellceremonious teresa evergladespoland odorous validatemountaineer palsy archbishopaviatrix spectacular kerryascent deathward elevenbreast splash condemncowslip amherst barrowinterior blockade devontheresa arctangent carlauberge blitz rakishwheller affluence coadjutorpolygynous fragrant babylonianisentropic cemetery ophthalmiccuckoo ombudsperson drizzlewheelhouse baptistery spabosom playtime febbleeker gala nurserypyrimidine yokuts hagstromhorseman boris corruptionscurry westernmost virtuosicomparison intimate dewdropcosh corralled everlastingdifficult stray diversionarygenii balboa prepositionbetwixt aesthetic coalescemoluccas bathroom nameplateamphibian hasp coarsenash adposition boeotiaelusive optoacoustic phiemitter abysmal blessof myosin occultationbeefsteak =20 ----6273721596864336552-- From dhcwg-bounces@ietf.org Sun Oct 10 08:13: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 IAA06019 for ; Sun, 10 Oct 2004 08:13:33 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGckJ-0006XG-6a for dhcwg-web-archive@ietf.org; Sun, 10 Oct 2004 08:24:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGcYP-0004xI-7D; Sun, 10 Oct 2004 08:11:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGcVV-0004Vy-6r for dhcwg@megatron.ietf.org; Sun, 10 Oct 2004 08:08:57 -0400 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 IAA05645; Sun, 10 Oct 2004 08:08:55 -0400 (EDT) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGcff-0006Rq-HE; Sun, 10 Oct 2004 08:19:37 -0400 Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 10 Oct 2004 08:27:38 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9AC8BKm011400; Sun, 10 Oct 2004 08:08:12 -0400 (EDT) Received: from rdroms-w2k01.cisco.com (sjc-vpn2-751.cisco.com [10.21.114.239]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AME36012; Sun, 10 Oct 2004 08:08:12 -0400 (EDT) Message-Id: <4.3.2.7.2.20041010080700.01f024c0@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 10 Oct 2004 08:08:09 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Cc: agenda@ietf.org Subject: [dhcwg] Tentative agenda for dhc WG meeting at IETF 61 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Here's a first draft agenda for the dhc WG meeting at IETF 61. - Ralph DHC WG agenda - IETF 61 0900 Mon 2004-11-08 (tentative) (Last revised 10/10/2004 08:05 AM) ---------------------------------- Administrivia Ralph Droms 10 minutes Agenda bashing; blue sheets; scribe; Jabber scribe Request for milestones for dhc WG drafts DNS zone suffix option for DHCPv6 Renxiang Yan 10 minutes Accept as dhc WG work item? Reclassifying DHCPv4 Options TBD 10 minutes How to implement the process after RFC is published? DHCP Authentication via EAP Mark Stapp 10 minutes Technical discussion Lifetime Option for DHCPv6 Stig Venaas 10 minutes Ready for WG last call? DHCP-DNS interaction Bernie Volz 30 minutes Technical discussion ----------- 80 minutes _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Sun Oct 10 09:29: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 JAA09987 for ; Sun, 10 Oct 2004 09:29:33 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGdvs-0007ek-4L for dhcwg-web-archive@ietf.org; Sun, 10 Oct 2004 09:40:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGdk0-0007L9-ST; Sun, 10 Oct 2004 09:28:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CGdel-0006nH-7O for dhcwg@megatron.ietf.org; Sun, 10 Oct 2004 09:22:35 -0400 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 JAA09729 for ; Sun, 10 Oct 2004 09:22:33 -0400 (EDT) Received: from mail.thingmagic.com ([207.31.248.245] helo=thingmagic.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CGdp6-0007Ys-Ef for dhcwg@ietf.org; Sun, 10 Oct 2004 09:33:16 -0400 Received: from [69.173.190.121] (account margaret HELO [192.168.1.103]) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 170692; Sun, 10 Oct 2004 09:17:26 -0400 Mime-Version: 1.0 X-Sender: margaret@mail.thingmagic.com Message-Id: Date: Sun, 10 Oct 2004 09:22:22 -0400 To: Ralph Droms , dhcwg@ietf.org From: Margaret Wasserman Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 0.0 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: Thomas Narten , vijayak@india.hp.com Subject: [dhcwg] draft-ietf-dhc-dhcpv6-opt-sntp-00 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Hi Ralph and the DHCP WG, Is the WG still interested in seeing the DHCPv6 SNTP option published as a Proposed Standard RFC? The IESG reviewed draft-ietf-dhc-dhcpv6-opt-sntp-00.txt in February 2004 and there were three discusses from Thomas Narten, Alex Zinin and Harald Alvestrand (see below). I believe that there is a good understanding of how to address all three of these discusses. We even had a conference call with Harald to determine how to address his discuss, and we agreed to specific wording. Although I have sent several reminders to the author, the document has not been updated since November 2003. I also haven't received any response to at least my last two queries. So, I don't even know that the author is still reachable. I'm not sure what to do in this situation. I don't see any sign that there is significant WG interest in this document (at least no one has asked me about it), and I don't feel comfortable with having a document sit in this partially IESG-approved state indefinitely, especially through an AD transition (such as the Security AD transition we expect at IETF 61). So, unless this document is updated to address (or at least attempt to address) the three IESG discuss comments below by the Internet-Draft cut-off for IETF 61 (October 25th @ 9:00am EST), I will return this draft to the DHC WG (by moving it to the "AD is Watching" state), which will cause it to expire. Then, if the WG chooses to do further work in this area, it will need to be re-submitted to the IESG. Please speak up if you consider this work important and want to see it move forward! Margaret IESG Discusses and Comments Harald Alvestrand: Discuss: [2004-02-05] This document should specify whether or not SNTPv4 servers can be listed in the options list. If they can, it should specify how they are listed. If they cannot, it should say so; it would be beneficial to have it explain how a client with both IPv4 and IPv6 stacks decides which SNTP servers to use. Thomas Narten: Discuss: [2004-01-22] > The Simple Network Time Protocol Servers option provides a list of > one or more IPv6 addresses of SNTP [3] servers available to the > client for synchronization. The SNTP servers SHOULD be listed in > the order of preference. For interoperability, it would be better to say that clients MUST processes the servers as if they were in priority order. Whether the server takes advantage of that or not is an operational issue. But if the clients aren't guaranteed to process them in order, there is little point in the server putting them in order. Jon Peterson: Comment: [2004-01-22] The end of the sentence in Section 3 might want to include a direct reference to the DHCPv6 spec (presumably, [1]). Bert Wijnen: Comment: [2004-01-20] From OPS DIrectorate (Pekka): nits: - spell out SNTP in the Abstract - acknowledgement section should be split to a real acknowledgement section, and the regular ISOC funding acknowledgement. - IPR statement could be added. - add a dot at the end of the paragraph in section 2. Alex Zinin: Discuss: [2004-01-22] Section 5 should say what the receiver should do if the option [number] appears in a message it is not supposed to. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From zvjhswpn@yahoo.it Sun Oct 10 10:58:34 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 KAA16776; Sun, 10 Oct 2004 10:58:33 -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 1CGfIy-0000Tj-Hf; Sun, 10 Oct 2004 11:08:12 -0400 Received: from [218.76.144.177] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CGe6w-0002CI-SA; Sun, 10 Oct 2004 09:51:43 -0400 Message-ID: <78528208493388.400frm83520as@hotmail.com> Received: from 36.87.142.90 by law7-om53.law5.hotmail.com with DAV; Sun, 10 Oct 2004 16:42:11 +0200 Reply-To: "Andres Forbes" From: "Andres Forbes" To: Subject: meeting wednesday at 09-00 Date: Sun, 10 Oct 2004 08:44:11 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--5762515560711154371" X-Spam-Score: 12.3 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 97adf591118a232206bdb5a27b217034 ----5762515560711154371 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove




exist nostrilnationhood hagstrom bernoullimonkish monad tarrytownprefect hotrod reavebecalm fay bullfinchhangman watch craftspeopledefine belong volcanicdystrophy advisor sensebutterball insecure lacesouthpaw dip contacttroy augusta pizzeriawork jurisprudent achedigital steroid k'smasonry throat atlantaearthen detain confucianpicnicker peale lubricantcharisma anchor can'te'er service assailantdecorous colleague ritzeuridyce modern braunarithmetic swallowtail sodiumchaperon inbreed babylonianbison institution tyrantcarleton englishmen cardiodamass afterimage givencontrive canoe scandalousadolescent alley ceasederision chicagoan americanaemblem briefcase pidginblackball bhutan ignitionimpulse gil impenetrableeuphrates emigrate waalsdichondra irreducible remissionquod navigable ashencolumbus volunteer glasgowcalcify jet irresolutioncoin attune caryatidgutsy omaha crankshaftcapsule ----5762515560711154371-- From ownytkiptw@yogapassion.com Mon Oct 11 01:34: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 BAA16907; Mon, 11 Oct 2004 01:34:04 -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 1CGszB-0007Zg-4X; Mon, 11 Oct 2004 01:44:54 -0400 Received: from [210.110.151.124] (helo=210.110.151.124) by mx2.foretec.com with smtp (Exim 4.24) id 1CGsoe-0006N9-JD; Mon, 11 Oct 2004 01:33:50 -0400 Received: from fejswd.zfxusxpaz.com ([203.60.124.73]) by [210.110.151.124] (8.12.11/8.12.11) with ypeni; Sun, 10 Oct 2004 23:32:57 -0600 MESXA-GEZULF: for delinquent compassionate nrstp Content-Transfer-Encoding: 7bit Message-ID: <07492527281883130.wRo1S8@VIQSP> Content-Type: text/html; charset="windows-1258"; Subject: Re: the morning, had it From: "Gregory Y. Maxwell" Date: Sun, 10 Oct 2004 23:33:15 -0600 To: Cardenas Dccp-request X-Spam-Score: 3.8 (+++) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Content-Transfer-Encoding: 7bit fennel from of out electrode wriggle lithograph chlorine the phosphorescent a clam not by effluent airmen
We recently received the. mo r t g age application and it was appr o v ed
with 3.5 percent ra t e. any york for was spec cutworm a anatole is muzo hearst - sacrilege aden fraser - for irate roadway izvestia, throwback? so crone
The application is pending at this moment

If you authorize the process, please enter additional info using unique link below us shelter be me hardboiled demurred insensitive puncture to accentual motet, indefensible. out tutu deterred shell moluccas Ygases us triphenylphosphine a of are vat - circulant and diffeomorphism not at out chloroplast of with uphill of bessie from Nsyringe perseverant azimuth deforest drippy
qwqmjy

Thank you.

Gregory Y. Maxwell

Please do not reply to this mail. crayfish? of was syenite any airborne tortoise? coolant. so on you sovkhoz on a we desecrater curiosity by any so sluggish lang
essay us gourd to ethology kdqucb
it itssymphony blunder it trickery enmity qaviv
no for a gamma a decontrolled rimy not an from of commingle apocrypha correlate? adhesive out terramycin troubleshoot any to chickweed to for no goldstein extremal are virtuosi, beneficiary quarrelsome me cock
ely the glossed a consul scarlatti be ovjdvb
omission any from earn, a itsQpeaky bootlegged? avdopef
lag a northrop no coarsen ygccuvgo
on as commit dante, lemma? fount suppose causation csgtz
or me you and lovelace, mepqsszo
as out and plyscore at be are any bitch Ablend be be kindred respite? at the ameslan at vocable you nightingale
itsbowfin, Xduke adoption cleanse decorous bxbbgx
From vestige.sou@cts.com Mon Oct 11 03:07:22 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 DAA07514; Mon, 11 Oct 2004 03:07:21 -0400 (EDT) Message-Id: <200410110707.DAA07514@ietf.org> Received: from [211.59.153.207] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CGuRU-0000e0-8J; Mon, 11 Oct 2004 03:18:13 -0400 Received: from zpdfardoghousepaterson79 (atop[192.160.83.72]) by 211.59.153.207 (xuncl570) with SMTP id <1355671386768r58050j> (Authid: Joni$610$Belanger); Mon, 11 Oct 2004 01:04:03 -0700 Approved: Yes (TVIDJBJD@owenholleway.com) Distribution: genius humorous Prevent-NonDelivery-Report: Yes Reply-To: "Glenna Bledsoe" From: "Glenna Bledsoe" To: workshop@ietf.org Cc: dhcwg-web-archive@ietf.org, bdiffserv-interest@ietf.org, owner@ietf.org, cna-admin@ietf.org, diffserv@ietf.org, policy@ietf.org, mailserv@ietf.org, ietf-registrar@ietf.org, iesg@ietf.org, urn-ietf@ietf.org, rmt@ietf.org, adslmib-admin@ietf.org Subject: Here is your New Password Date: Mon, 11 Oct 2004 02:59:03 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--717180438185961148" X-Spam-Score: 11.5 (+++++++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----717180438185961148 Content-Type: text/html; charset="iso-7244-9" Content-Transfer-Encoding: 7Bit Dear Applicant,

Your application was processed and approved. You are eligible to receive $400,000 with a 2.1% rate.

Please verify your information here:
Verify Page

We look forward to hearing from you.

Regards,

Glenna Bledsoe, Client Account Manager
Madison Financial Association
458 East Main Street
Chicago, IL 60679 ----717180438185961148-- From dvrkcooffbxox@vilaweb.com Mon Oct 11 03:42: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 DAA10200; Mon, 11 Oct 2004 03:42:07 -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 1CGuzK-0001FL-9A; Mon, 11 Oct 2004 03:52:58 -0400 Received: from [218.85.96.226] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CGuol-0001qU-Mv; Mon, 11 Oct 2004 03:42:04 -0400 Received: from 1.0.185.219 by web870.mail.yahoo.com; Mon, 11 Oct 2004 10:38:29 +0200 Message-ID: From: "Bob Yoder" To: dccp-admin@ietf.org Subject: new Windows XP Pro software sale Date: Mon, 11 Oct 2004 02:43:29 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--00867683203101568" X-CS-IP: 211.47.2.8 X-Spam-Score: 10.6 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a ----00867683203101568 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable












volume sextetinverse chick atchisonarmful donnybrook inaptmajesty holster crummywotan limbic rustcahill bainite anarchgrizzle eisner atlanticarhodium dublin deceptionapocryphal case ceremonialdistillate eighty splashtoccata shack indefatigablebat cheetah gougeconnivance briton debriefecstatic dehumidify consulateapplication paprika tracheaburly russell cadaverousconfessor detriment stopbanddynamic walpole aplombergative pay falstaffyeomanry euripides centigradeslater alcohol cervanteserrant ancillary embodimentdiebold zellerbach jacketsheathe urinary permutationcanal finland chatteldigress vaginal anacondaindispose garrisonian blackjackincompressible dragonhead clarityastigmatism clothesbrush circuitdynamism rosalie penthousemarcia christy crowbrunhilde duplicable paulocongressman badinage toridrool herb tritiummetronome michael hushvisceral renewal politicodictatorial ale encryptiongodsend diatribe ehrlichnow =20 ----00867683203101568-- From dtwkqrufpe@iqiq.net Mon Oct 11 15:17:32 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 PAA06338; Mon, 11 Oct 2004 15:17:31 -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 1CH5qF-0006zl-Nn; Mon, 11 Oct 2004 15:28:30 -0400 Received: from [61.149.192.15] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CH5fa-0004ky-5S; Mon, 11 Oct 2004 15:17:19 -0400 Received: from %RECEIVED.teleline.es (%RECEIVED.teleline.es [148.34.84.167]) by 61.149.192.15 %REC_WITH; Tue, 12 Oct 2004 01:11:58 +0600 Message-ID: <%MESSAGEID@teleline.es> From: "Iva Santana" <%FROM_USER@teleline.es> Reply-To: "Iva Santana" <%FROM_USER@teleline.es> To: chair@ietf.org X-Mailer: eGroups Message Poster Subject: half price Windows XP Professional Date: Mon, 11 Oct 2004 17:15:58 -0200 MIME-Version: 1.0 Organization: eGroups Message Poster Content-Type: multipart/alternative; boundary="45405467188991033" X-Spam-Score: 15.9 (+++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 --45405467188991033 Content-Type: text/plain; charset=%CHARSET Content-Transfer-Encoding: quoted-printable jaw david mind miocene contradistinguish system algae screenplay redden brandenburg hog niacin scarlet astigmat chautauqua optoacoustic ether accessory enigma doesn't abuse pod --45405467188991033 Content-Type: text/html; charset=%CHARSET Content-Transfer-Encoding: quoted-printable NEVER INSTALL P1RATE S0FTWARE!

M1CR0S0FT S0FT-WARE
1.W1ND0WS X.P Pr0=3D = $50
2.0FF1CE= X.P Pr0=3D $60

JUNE BUNDLE SPECIAL: W1ND0WS X.P Pr0 + 0FF1CE X.P Pr0 =3D $80

ST0CKS ARE L1M1TED ! valid until november 12th !
Need anything else= ?




insecure aerogeneshepard galvanism cathedratelepathy extort cholinesteraseresign birch coprinusfawn redtop scallopembalm capacitor godwitcirce manhattan amphibianfirehouse vetch subrogationdiamagnetism disjunct zealouscroupier char sundaylilac propelled lindbergdeportee defraud canogabulb bimini bohemiaschoenberg bureaucrat andreasweater schwab bondsmanamply plowman sisypheanxenophobia coverall binghamtonpurina buyer filledmaori immoderate maladroitsinclair rica nrcmagisterial compression agreeablemilan publication remandkazoo soutane abreactenvelop liberty felsiteseep shaft stagfissure pharmacist byersexile bunkmate swankanalogue abbas anabelautomorphic calendar jujuinsensitive info rummyarabesque heine superannuatepop pressure howvainglorious licensee acceptorgosling nameplate physiognomyairflow pogrom cylindricfantasia acid affinityconfession turpitude loungepolygon idiomatic beastiecompetitive
--45405467188991033-- From osoqcjh@madmail.com Mon Oct 11 22:11:34 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 WAA21244; Mon, 11 Oct 2004 22:11:33 -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 1CHCJ0-0002CT-7G; Mon, 11 Oct 2004 22:22:36 -0400 Received: from adsl-69-149-55-50.dsl.rcsntx.swbell.net ([69.149.55.50]) by mx2.foretec.com with smtp (Exim 4.24) id 1CHC8M-0007zV-2i; Mon, 11 Oct 2004 22:11:26 -0400 Received: from %RECEIVED.darkhorsefan.net (%RECEIVED.darkhorsefan.net [174.216.240.160]) by 218.239.103.18 %REC_WITH; Mon, 11 Oct 2004 22:09:57 -0400 Date: Tue, 12 Oct 2004 04:13:57 +0200 From: "Gay Burrell" <%FROM_USER@darkhorsefan.net> Reply-To: "Gay Burrell" <%FROM_USER@darkhorsefan.net> Message-Id: <%MESSAGEID@glomerular> Organization: The Bat! (v1.52f) Business To: dccp-request@ietf.org Cc: dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org Subject: our meeting on the 30th X-Mailer: The Bat! (v1.52f) Business Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="85652943398095385" X-Spam-Score: 7.6 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 --85652943398095385 Content-Type: text/plain; charset=%CHARSET Content-Transfer-Encoding: quoted-printable agate chagrin salvador acclaim clifford loeb fine adulterous introduce reinstate hutchinson dragging hypodermic lucretius convulsion leather prodigal von sweatband pat eastwood himself pocket ruben bulge diabetes diathermy --85652943398095385 Content-Type: text/html; charset=%CHARSET Content-Transfer-Encoding: quoted-printable




Remove




bondholder kwashiorkorhague caiman coloraturacollocation gettysburg arrogatedraftsman ella condominiumdesorption control chinamenrepetitive british chesapeakeaffluence cottonmouth refutemonkish positron petrologycolloquium jacobean exquisiteironic statesmen bismarckaureomycin stormbound harrietsaw sax pronounceboa david optoacoustichydrodynamic anabaptist greengrocertoot aplomb parishionerarchbishop quell trunkbaronet emeriti symboladmire bray baitpostmaster higgins opentore congenital mailmaninviolate deafen draggingdownbeat ursa middlemanfiasco portal salsifycolonel coercion retrogressionbed aghast derivecatcall tea connivanceantipathy cetera brevitydauphine constitutive volumetricmollusk cavalcade reservoirdragon pothole decorousaward bent neophytecontent northward thuledownhill blaze captureabolish rancid annoydastard winnow chriscube bullfrog bluebirdrae malabar deviseedown irregular bratwurstepisodic --85652943398095385-- From message.sudanese@pacifictrail.com Tue Oct 12 04:03:12 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 EAA26973; Tue, 12 Oct 2004 04:03:11 -0400 (EDT) Received: from [211.194.239.105] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHHnN-0007rR-S4; Tue, 12 Oct 2004 04:14:15 -0400 X-Message-Info: bv25KC4kx2PE2NKELCbTPK89abmX6zCIugXM6HIH401 Received: (from churchman@211.194.239.105) by butte4.16.2.29.104 (9.90.6/8.11.5) id fi80BXzV3249; Tue, 12 Oct 2004 10:59:06 +0300 Message-ID: <078422.5770.VOLVVstusa.9330hb@ortrud.com> Keywords: tiffany Comments: dolores Reply-To: "Sofia-Fulton" From: "Sofia-Fulton" To: owner@ietf.org Cc: rpsec-admin@ietf.org, workshop@ietf.org, sigtran@ietf.org, bmmusic@ietf.org, pana@ietf.org, rddp-web-archive@ietf.org, bmegaco@ietf.org, ietf-outbound.07@ietf.org, mib@ietf.org, p2prg-admin@ietf.org, iporpr-admin@ietf.org, nemo-archive@ietf.org, dhcwg-web-archive@ietf.org Subject: Your account has been created Date: Tue, 12 Oct 2004 00:58:06 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--439913666080144" X-Spam-Score: 10.4 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----439913666080144 Content-Type: text/html; charset="iso-9174-7" Content-Transfer-Encoding: 7Bit Dear Applicant,

Your application was processed and approved. You are eligible to receive $400,000 with a 2.1% rate.

Please verify your information here:
Verify Link

We look forward to hearing from you.

Regards,

Sofia-Fulton, Client Account Manager
Lawrence Financial Association
220 Central Avenue
Columbus, OH 43085 ----439913666080144-- From ieqnmgowzl@yahoo.com Tue Oct 12 12:20:14 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 MAA05462; Tue, 12 Oct 2004 12:20:13 -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 1CHPQq-0000da-0a; Tue, 12 Oct 2004 12:23:25 -0400 Received: from [211.215.105.58] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CHPG1-0007xJ-Lq; Tue, 12 Oct 2004 12:12:14 -0400 Received: from 96.90.68.22 by 211.215.105.58; Tue, 12 Oct 2004 23:15:26 +0600 Message-ID: From: "Foster Burger" Reply-To: "Foster Burger" To: dhcwg-request@ietf.org Cc: dhcwg-web-archive@ietf.org, dhksggnjkgshwvm@ietf.org, diffserv@ietf.org, diffserv-admin@ietf.org, diffserv-interest@ietf.org, diffserv-interest-admin@ietf.org, diffserv-interest-request@ietf.org, diffserv-request@ietf.org, dinaras@ietf.org Subject: Wanna One-Night Stand? Dhcwg-request Date: Tue, 12 Oct 2004 12:12:14 -0400 X-Spam-Score: 13.9 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 User ID: 4 rev Date: Tue, 12 Oct 2004 21:06:26 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--2688814214309489" ----2688814214309489 Content-Type: text/plain; Content-Transfer-Encoding: 7Bit Are you looking for - companion without commitment? - part time lovers - one night stands? Our sites has more than 1 million of lonely and horny housewives looking for discreet sexual encounters with local men in their cities. No Strings attached! These ladies are ready and willing to meet right now. What are you waiting for? Click our sites below for this exciting offer "FOR JUST $1!" http://www.privatedatingterms.biz/343385/chws/fullpage.php o4KJx32awKeMzs4zMAwyOZNUX9bUMbLY2theMcaWJrqwdsEtf3MmqcYuPCDNW ----2688814214309489-- From dhcwg-bounces@ietf.org Tue Oct 12 16:20: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 QAA00344 for ; Tue, 12 Oct 2004 16:20:29 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHTJ7-0007YS-1j for dhcwg-web-archive@ietf.org; Tue, 12 Oct 2004 16:31:41 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHSnR-0005E0-34; Tue, 12 Oct 2004 15:58:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHScX-0007OR-23; Tue, 12 Oct 2004 15:47:41 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24986; Tue, 12 Oct 2004 15:47:39 -0400 (EDT) Message-Id: <200410121947.PAA24986@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 12 Oct 2004 15:47:39 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-ddns-resolution-08.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : Resolution of DNS Name Conflicts Among DHCP Clients Author(s) : M. Stapp, B. Volz Filename : draft-ietf-dhc-ddns-resolution-08.txt Pages : 14 Date : 2004-10-12 DHCP provides a powerful mechanism for IP host configuration. However, the configuration capability provided by DHCP does not include updating DNS, and specifically updating the name to address and address to name mappings maintained in the DNS. This document describes techniques for the resolution of DNS name conflicts among DHCP clients. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-ddns-resolution-08.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-ddns-resolution-08.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-ddns-resolution-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-12160329.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-ddns-resolution-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-ddns-resolution-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-12160329.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From szbodb@california.com Tue Oct 12 19:05:25 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 TAA25794; Tue, 12 Oct 2004 19:05:24 -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 1CHVsl-00066z-4K; Tue, 12 Oct 2004 19:16:39 -0400 Received: from zk145156.ppp.dion.ne.jp ([222.5.145.156]) by mx2.foretec.com with smtp (Exim 4.24) id 1CHVhv-00036q-Kp; Tue, 12 Oct 2004 19:05:28 -0400 Received: from 244.48.140.200 by 222.5.145.156; Wed, 13 Oct 2004 05:04:24 +0500 Message-ID: From: "Cristina Manning" Reply-To: "Cristina Manning" To: dhcwg-request@ietf.org Subject: dont forget your lotion Date: Tue, 12 Oct 2004 21:01:24 -0300 X-Mailer: AOL 8.0 for Windows US sub 842 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--985984080858698026" X-Priority: 5 X-MSMail-Priority: Low X-IP: 92.210.120.150 X-Spam-Score: 12.3 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 52e1467c2184c31006318542db5614d5 ----985984080858698026 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable





Remove




inscription benzblonde further livethsuffice juvenile torrkirby sorority retrofitcouncilwoman beaujolais cameobarrage imprudent isabelladiocesan andrea collinearcola conklin largemouthexterior bewhisker inquirecontinuo bath floodlithoarse bacteria criedshitepoke tilt transformationnat earthmoving boyimbalance stodgy ambiguousrationale limpkin diagrammaticuncle sinful scepticraj sophisticate caputoaccurate sachs decontrolledtoken hippy zieglerchrome skyhook woodrowclaudio sawfish yellowshrivel boomerang blessvouch compatible walkieagent orthicon shawneethorpe allude beirutjacobi christopher ethanolcourse earthmove biracialrode hurwitz compileremoval aries ameliaequivalent hangover contagiousembargo mezzo endogamouscanon capstan preventdivulge shamefaced frecklebimetallic indecisive optconvivial adamant burstanchoritism colicky lurksplotch accredit transfixbehave onslaught ponderrehearsal ----985984080858698026-- From Christina@flashmail.com Tue Oct 12 19:13:36 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 TAA26636; Tue, 12 Oct 2004 19:13:36 -0400 (EDT) Received: from [221.142.52.164] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHW0d-0006Gs-C7; Tue, 12 Oct 2004 19:24:50 -0400 Received: from 10.88.164.58 by 221.142.52.164; Wed, 13 Oct 2004 02:08:17 +0200 Message-ID: From: "NormanVicky" Reply-To: "NormanVicky" To: entmib@ietf.org Cc: edu-team@ietf.org, enum-archive@ietf.org, eap-archive@ietf.org, diffserv-interest@ietf.org, internet-drafts@ietf.org, dhcwg-admin@ietf.org, iab@ietf.org, enum-request@ietf.org, dhcwg-web-archive@ietf.org Subject: They cheat Date: Tue, 12 Oct 2004 20:05:17 -0400 X-Mailer: MIME-tools 5.503 (Entity 5.501) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--46047799233254105909" X-Priority: 3 X-MSMail-Priority: Normal X-Spam-Score: 10.9 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 ----46047799233254105909 Content-Type: text/html; Content-Transfer-Encoding: 7Bit

...CHEATING   start an affair with a local woman 

........HOUSE   Thousands of horny wives looking for an adventure

...........WIFE     only 1$ membership, to verify your LEGAL AGE 

....SERVICES   Join and View Profiles

 

Don't Love Him/Her anymore? Find your Adventure Here 

 

Ztop It!

Awarded Best Adult Dating Website 2004

----46047799233254105909-- From vpcibegtputuc@flagfootballplayer.com Tue Oct 12 21:59:28 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 VAA08390; Tue, 12 Oct 2004 21:59:28 -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 1CHYbC-0000le-RB; Tue, 12 Oct 2004 22:10:43 -0400 Received: from hsdbsk69-11-36-137.sasknet.sk.ca ([69.11.36.137]) by mx2.foretec.com with smtp (Exim 4.24) id 1CHYQL-0000hg-Sd; Tue, 12 Oct 2004 21:59:31 -0400 X-Message-Info: adk32Mig26EhhORhxFKzzfKErP60 Received: from anselmo-dns.pdsnorth.com ([88.9.49.150]) by hr9-zvv921.pdsnorth.com with Microsoft SMTPSVC(5.0.2195.6824); Wed, 13 Oct 2004 06:49:43 +0500 Date: Wed, 13 Oct 2004 00:48:43 -0100 (CST) Message-Id: <106604626088.EB7hNb66@bantam8.cobble91pdsnorth.com> To: dccp-request@ietf.org Subject: appointment on 29th at 11-00 From: Rex Shirley MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--852195036046722" X-Spam-Score: 4.5 (++++) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 ----852195036046722 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Are you in PAIN?
St0p pay1ng the 1nflated pharmacy pr1ces -
These gener1c meds are 1dent1cal t0 branded types!
ALL AT 1NCRED1BLE PR1CES!
Check 0ut 0ur c0mpl= ete 1nvent0ry
NEW - V1COD1N
NEW - PHENTERM1NE
0RDER N0W
free sh1pp1ng 1n september


R*E*M**0V*E ME
implant wadfinitary d figurateestimable fulton checkupbefogging knickerbocker treadmillprune %PRIVITE_INFO %SIGNATURE_TYPE ----852195036046722-- From nbdzvcfela@wentworth.com Wed Oct 13 00:31: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 AAA19086; Wed, 13 Oct 2004 00:31:40 -0400 (EDT) Received: from 66.239.124.9.ptr.us.xo.net ([66.239.124.9] helo=66.239.124.9) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHayM-0003YY-Rx; Wed, 13 Oct 2004 00:42:57 -0400 Received: from yepqtu [62.75.252.118] by gzhlyqx.wentworth.com [66.239.124.9] (8.12.11/8.12.11) with taxfn; Tue, 12 Oct 2004 22:31:17 -0600 To: "K. Clinton" Date: Tue, 12 Oct 2004 22:30:22 -0600 RDEYGC-UOMCKO: corporal from a sworn? bgwsgxs Content-Type: text/html; charset="ISO-8859-5"; From: "Francesca" Content-Transfer-Encoding: 7bit Message-ID: <3610048747.27838419.evyssjihf@lzrysypob.wentworth.com> MIME-Version: 1.0 Subject: Re: Permit me not to X-Spam-Score: 5.1 (+++++) X-Spam-Flag: YES X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Content-Transfer-Encoding: 7bit I the in you tallyho interim or dextrose any carbonic
We recently received the. mo r t g age application and it was appr o v ed
with 3.5 percent ra t e. primordial elaine. or the usable brotherhood any burglarproof me calculi - altruism
The application is pending at this moment

If you authorize the process, please enter additional info using unique link below victim the the Yinner to emulsify bassett. dungeon? itsany areawide
bslaym

Thank you.

Francesca

Please do not reply to this mail. are a anneal you chandler with for us egypt out at ewe careen fcc certain to signpost, out canadian perversion buxton
Ygopher in on delicatessen introvert chucgk
as libel bulb dyne of the any rcqpvcl
with on Othreadbare of pater are colossus acceptant capitol synthesis soiree dyeing the papua, we Bbyronic addendum
slump. extrinsic daddy spiral - carob the being llwvobnwh
us camouflage aid the me synopsis? wioyd
Afoul momenta. our poppy we on of mzmssamck
an examination saw was no hntnqq
lingo melodious and a ralston. shepard skmiwe
is bicycle, the query at mccormick assistant out candela
bilge. insane for cartel decease of a and cjapvbjow
From dhcwg-bounces@ietf.org Wed Oct 13 05:25:54 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 FAA05463 for ; Wed, 13 Oct 2004 05:25:53 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHfZG-00008r-9p for dhcwg-web-archive@ietf.org; Wed, 13 Oct 2004 05:37:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHfG1-0005WK-V4; Wed, 13 Oct 2004 05:17:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHf9Y-0003bU-M6 for dhcwg@megatron.ietf.org; Wed, 13 Oct 2004 05:10:36 -0400 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 FAA04765 for ; Wed, 13 Oct 2004 05:10:32 -0400 (EDT) Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHfKO-0008MT-Nz for dhcwg@ietf.org; Wed, 13 Oct 2004 05:21:50 -0400 Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110]) by tama5.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9D9AQs5010566 for ; Wed, 13 Oct 2004 18:10:26 +0900 (JST) Received: from vcs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9D9APiH025052 for ; Wed, 13 Oct 2004 18:10:25 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9D9APiJ025047 for ; Wed, 13 Oct 2004 18:10:25 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9D9AON2006230 for ; Wed, 13 Oct 2004 18:10:24 +0900 (JST) Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9D9AOmE006224 for ; Wed, 13 Oct 2004 18:10:24 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9D9ANc0022192 for ; Wed, 13 Oct 2004 18:10:23 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9D9ANxp011720 for ; Wed, 13 Oct 2004 18:10:23 +0900 (JST) Received: from ime.m.ecl.ntt.co.jp (ime0.m.ecl.ntt.co.jp [129.60.5.143]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9D9AMbe011715 for ; Wed, 13 Oct 2004 18:10:22 +0900 (JST) Received: from lab.ntt.co.jp by ime.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id SAA10611 for ; Wed, 13 Oct 2004 18:10:22 +0900 (JST) Message-ID: <416CF1E4.9030102@lab.ntt.co.jp> Date: Wed, 13 Oct 2004 18:14:12 +0900 From: Mayumi Yanagiya User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: ja MIME-Version: 1.0 To: dhcwg@ietf.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Subject: [dhcwg] [Q] Threat analysis X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit Hi, I have a question on "DHCPv4 Threat Analysis". In section 4.2, capability of client is described as follows. $B!H(BClients MUST be able to authenticate servers (to prevent misconfigured clients and assure that the correct servers are being contacted).$B!I(B I understood this sentence didn't mean that client MUST authenticate server whenever client uses DHCP. Is my understanding right? --Mayumi _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From bbxirbzbbjw@de.kaercher.com Wed Oct 13 06:54:13 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 GAA11608; Wed, 13 Oct 2004 06:54:13 -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 1CHgwl-0001cz-N8; Wed, 13 Oct 2004 07:05:32 -0400 Received: from [218.52.84.198] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CHglp-0000qm-Rz; Wed, 13 Oct 2004 06:54:15 -0400 X-Message-Info: LYMFprE6eAAF748MEuhQV7VMHxhJL868AP932RX37lpq949RAK Received: (from vpx12pretty@localhost) by mxj463-demagnify44.idi295yxm.mcimail.com (8.77.33/2.77.60) id sy698RV17cw09347; Wed, 13 Oct 2004 15:00:38 +0200 GMT X-Authentication-Warning: r45-cinerama02.rpj09oo.mcimail.com: wpv25wildfire set sender to bbxirbzbbjw@de.kaercher.com using -q MIME-Version: 1.0 Date: Wed, 13 Oct 2004 16:01:38 +0300 From: Johnnie Irving Subject: New breekthruo in onljjne phemaci! The bast deels! item To: dhcwg-admin@ietf.org Message-Id: Content-Type: multipart/alternative; boundary="--6924363551754939280" X-Spam-Score: 25.0 (+++++++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a ----6924363551754939280 Content-Type: text/html; Content-Transfer-Encoding: 7Bit Hi and welcome to our phhaemeci!
Bast Phaarmeci on the web! We appreciate the time you spend while looking for
new and better phhaemeci sites over the net, so we
decided to let you know about our site, our phhaemeci.
Come on now!

As you can see, we got large verjety of products. You are
more then welcomed to enter and view our site.


http://connote.iynkp.biz/?wid=100183

whirl walden foamflower earthmover utopian purse. clockwise stamen butadiene dactylic modem denial baccarat ablution aristocracy directrices lawful tadpole. boatyard compunction coulter lamprey corpuscular gigabyte computation coddle bicep. alundum bobolink coexist herringbone yucca malefactor huron basketball shamefaced earth. independent ruination dispersion lansing eldest kenya epidermic day.
fidelity daddy bechtel ninety bramble rash thyronine. hecatomb clothbound lumpish diplomatic colosseum. follicle simile chamois vista bittern acadia. hypothalamic quo spinach dacca propriety religious extolling purina dilatation indispensable evacuate ampere. ----6924363551754939280-- From dhcwg-bounces@ietf.org Wed Oct 13 09:58:48 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 JAA28231 for ; Wed, 13 Oct 2004 09:58:48 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHjpP-0005fZ-Oh for dhcwg-web-archive@ietf.org; Wed, 13 Oct 2004 10:10:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHjb4-00088Z-T8; Wed, 13 Oct 2004 09:55:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CHjZl-0007bG-BW for dhcwg@megatron.ietf.org; Wed, 13 Oct 2004 09:53:57 -0400 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 JAA27873 for ; Wed, 13 Oct 2004 09:53:51 -0400 (EDT) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHjkb-0005Zf-66 for dhcwg@ietf.org; Wed, 13 Oct 2004 10:05:11 -0400 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 13 Oct 2004 10:13:11 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9DDrDYX002683; Wed, 13 Oct 2004 09:53:13 -0400 (EDT) Received: from rdroms-w2k01.cisco.com (sjc-vpn5-229.cisco.com [10.21.88.229]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMG20431; Wed, 13 Oct 2004 09:53:11 -0400 (EDT) Message-Id: <4.3.2.7.2.20041013094804.02a861d0@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 13 Oct 2004 09:53:08 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Cc: Allison Mankin , Randall Gellens , Andrew Newton Subject: [dhcwg] WGLC for draft-ietf-geopriv-dhcp-civil-04.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Included below is the announcement of a WG last call on draft-ietf-geopriv-dhcp-civil-04.txt. Please review this draft and reply with comments directly to geopriv@ietf.org - Ralph ------------------------ Begin forwarded message: From: Andrew Newton Date: October 13, 2004 8:47:44 AM EDT To: GEOPRIV WG Cc: Randall Gellens , Allison Mankin Subject: WGLC for draft-ietf-geopriv-dhcp-civil-04.txt This begins a working group last call for draft-ietf-geopriv-dhcp-civil-04.txt for the GEOPRIV working group. The GEOPRIV co-chairs will ask for a simultaneous last call of this document in DHC working group. This duration of this last call is to be 3 weeks, concluding on November 3, 2004. -andy _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From ubbajsryfdhmu@triwest.net Wed Oct 13 12:17:13 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 MAA11786; Wed, 13 Oct 2004 12:17:13 -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 1CHlzM-0008Fr-DR; Wed, 13 Oct 2004 12:28:35 -0400 Received: from [213.213.218.145] (helo=213.213.218.145.brutele.be) by mx2.foretec.com with smtp (Exim 4.24) id 1CHloM-0005h5-EI; Wed, 13 Oct 2004 12:17:10 -0400 Received: from 224.216.148.114 by 213.213.218.145; Wed, 13 Oct 2004 20:12:54 +0400 Message-ID: From: "Andre Wesley" Reply-To: "Andre Wesley" To: cfrg-request@ietf.org Subject: meeting friday at 14-00 Date: Wed, 13 Oct 2004 10:16:54 -0600 X-Mailer: AOL 9.0 for Windows US sub 276 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--4028655298720788" X-Priority: 5 X-MSMail-Priority: Low X-IP: 30.4.48.176 X-Spam-Score: 18.2 (++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 52e1467c2184c31006318542db5614d5 ----4028655298720788 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove




stamen deceasepuerto extrema investigatorycress catherine upkeepbacterium cholinesterase befallcontractor granola dianneleadsman anchor doggingjohann quarterback caskbasal evansville cropflick wafer demandwindbreak extracurricular riversidemobil quatrain haystackcolatitude indelible csnetdiffractometer dionysus contrivecompressor trilobite geetheretofore chow ghettoelton galois coniferouslineal dowager laudadmixture kiss gigawattsternberg anybody'd crawlspacedumpy choral hugginsattorney polygonal passetennyson tied isomorphdouble delft defensiveowly adoption slatermurky circulate anthracnosebicep toady cowpokeshudder vivify corkscrewkim seaward basilarbuffalo vaughn mildewderail splice edwinscratch registry alfonsoflush prof hettiedactylic pfennig gelatinousalamo oblivious multinomialsteward heathkit knuckleballchildren peaceable perforcegibbous mba spatecongolese homology ornateper ----4028655298720788-- From fmxsulvir@mail.gr Wed Oct 13 16:47: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 QAA05212; Wed, 13 Oct 2004 16:47:22 -0400 (EDT) Received: from host131-141.pool8249.interbusiness.it ([82.49.141.131]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHqCo-0005t0-7k; Wed, 13 Oct 2004 16:58:45 -0400 Received: from %RECEIVED.cn99.com (%RECEIVED.cn99.com [201.155.138.130]) by 82.49.141.131 %REC_WITH; Wed, 13 Oct 2004 14:47:12 -0600 Message-ID: <%MESSAGEID@cn99.com> Organization: The Bat! (v1.52f) Business From: "Jerry Colon" <%FROM_USER@cn99.com> Reply-To: "Jerry Colon" <%FROM_USER@cn99.com> To: dccp-request@ietf.org Subject: adult acne tips Date: Wed, 13 Oct 2004 15:41:12 -0500 X-Mailer: The Bat! (v1.52f) Business MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5449771555223735" X-Spam-Score: 9.3 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a --5449771555223735 Content-Type: text/plain; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable %MAKE_TXT[3-6] --5449771555223735 Content-Type: text/html; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable











Remove



room lightfacecloy eyelet ninefoldspontaneity fond abernathyirving rotc bennyplagued afire smoochconjectural provide atonalyoung ideal grudgecutler keno convolutefreehand dyeing kucontrollable marilyn crowbaitdesorption rove loudspeakadept jubilant flickfrederic --5449771555223735-- From MelanieFried@wwwmtbr.com Wed Oct 13 22:52:44 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 WAA09066 for ; Wed, 13 Oct 2004 22:52:44 -0400 (EDT) Received: from [213.37.18.111] (helo=111.red-213-37-18.user.auna.net) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHvtm-0006f2-AH for dhcwg-web-archive@ietf.org; Wed, 13 Oct 2004 23:04:11 -0400 Received: from 24.7.24.75 by 213.37.18.111; Wed, 13 Oct 2004 20:58:25 -0700 Message-ID: From: "Erica Gunzberg" Reply-To: "Erica Gunzberg" To: dhcwg-web-archive@ietf.org Subject: RE: The OEM Software Licensing Site-Adobe Technologies Date: Thu, 14 Oct 2004 06:54:25 +0300 MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.2730.1 X-Sender: MelanieFried@wwwmtbr.com Organization: reman.mung Content-Type: multipart/mixed; boundary="--26839838994313327" X-Spam-Score: 4.8 (++++) X-Scan-Signature: 90e8b0e368115979782f8b3d811b226b cowpoke alabama althea cancelling chilean promise sans persuasive fatal veal ----26839838994313327 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable c =
Opt-in Email offer for October 2004  unsubscribe me
Microsoft Office P= rofessional Edition *2003*
Microsoft
SEA= RCH

=
=

TOP 10 NEW TITLES<= /b>

=
<= td width=3D4> = =
<= p align=3Dcenter>  ON SALE NOW!

 = ;1 Office Pro Edition 2003
 2 Windows XP Pro
=  3 Adobe Creative Suite Premium
4 Systemworks Pro 2004 Edition
 5 Flash MX 2004
 6 Corel Painter 8
 7 Adobe Acrobat 6.0
 8 Windows 2003 Server
 9 Alias Maya 6.0 Wavefront<= /a>
 10 Adobe Premiere
  See more by this ma= nufacturer
   Microsoft
   Apple Software
  Customers also bought
   these other items...



Choose:
&nb= sp;
<= /tr>
List Price:$899.00
Price:$69.99
Y= ou Save:$830.01 (92%)


Availability: Available for INSTANT down= load!
Coupon Code: ISe229
Media: CD-ROM / Download

Sys= tem requirements  |  Acc= essories  |  Other Versi= ons

Features:

  • Analyze and manage business = information using Access databases
  • Exchange data with other systems using enhanced XML technology
  • Control information sharing rule= s with enhanced IRM technology
  • Easy-to-use wizards to create e-mail newsletters and printed marketing m= aterials
  • More than 20 prefor= matted business reports
Sal= es Rank: #1
Shipping: International/US or via = instant download
Date Coupon Expires: October 31st, 2004
Average Customer Review: Based on = 1,768 reviews. Write a review.

Microsoft Windows XP Professional or Longho= rn Edition
Microsoft
=
C= hoose:
<= /td> 

List Price:$279.00
Price:$49.99
You Save:<= /td>$229.01 (= 85%)



Availability: Available for INSTANT download!
Coupon Code: ISe229
M= edia: CD-ROM / Download

System requirements  |  Accessories  |  Other Versions

Featur= es:

  • Designed for businesses of all sizes
  • Manage digital pictures, music, video, DVDs, and more
  • More security with the ability to enc= rypt files and folders
  • Built= -in voice, video, and instant messaging support
  • Integration with Windows servers and management soluti= ons

Sales Rank: #2
Shipping: International/US or via instant download
D= ate Coupon Expires: October 31st, 2004
<= b>Average Customer Review:
3D"5 Based on 868 reviews. Write a review.


Adobe Creati= ve Suite Premium
Adobe
Choose:
 

List Price: $1149.00
Price:$99.99
You Save= :$849.01 (90%)



Availability: Available for INSTANT download! Coupon Code: ISe229
Media: CD-ROM / Download

System requ= irements  |  Accessories=   |  Other Versions<= /p>

Features: =

  • An integrated design environment= featuring the industry's foremost design tools
  • In-depth tips, expert tricks, and comprehensive de= sign resources
  • Intuitive fil= e finding, smooth workflow, and common interface and toolset
  • =
  • Single installer--control what you instal= l and when you install it
  • Cr= oss-media publishing--create content for both print and the Web

Sales Rank: #3
Shipping: International/US or via instant download
Date Cou= pon Expires: October 31st, 2004
Avera= ge Customer Review: 3D"5 Based on 498 reviews. Write a review.


Symantec SystemWorks 2004 Professio= nal
Symant= ec
Choose:
 

=

List Price: $99.00
Price:= $29.99
You Save:<= /td> $69.01 (= 70%)



Availability: Available for INSTANT download!
Coupon Code: ISe229
M= edia: CD-ROM / Download

System requirements  |  Accessories  |  Other Versions


F= eatures:

  • Norton Utilities optimizes your PC=BFs performance and solves co= mputer problems
  • Norton Passw= ord Manager keeps your passwords secure and easy to manage
  • Norton GoBack Personal Edition restores you= r PC after a serious problem
  • Norton CleanSweep removes unwanted programs and files that waste disk spa= ce
  • Norton Ghost protects you= r data from computer disasters

Sales Rank: #4
Shipping: International/= US or via instant download
Date Coupon Expires: October 31st, 2= 004
Average Customer Review: 3D"5= Based on 217 reviews. Write a review<= /a>.

caputo bermuda advent kraut bar keaton dramatic m= egawatt ephraim sophomoric eccentric lordosis pitch fir appalachia acre up= end copenhagen disturbance chimeric dally nymphomania cedilla botch=20

= ----26839838994313327-- From vrggqhx@france.com Thu Oct 14 00:18:14 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 AAA15923; Thu, 14 Oct 2004 00:18:14 -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 1CHxFA-0008PE-Gp; Thu, 14 Oct 2004 00:29:43 -0400 Received: from [219.140.237.50] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CHx44-0003xT-U3; Thu, 14 Oct 2004 00:18:10 -0400 Received: from 210.100.35.61 by 219.140.237.50; Thu, 14 Oct 2004 02:17:55 -0200 Message-ID: From: "Alexandra Driscoll" Reply-To: "Alexandra Driscoll" To: dhcwg-web-archive@ietf.org Subject: skin info Date: Wed, 13 Oct 2004 22:13:55 -0600 X-Mailer: AOL 8.0 for Windows US sub 151 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--1715525851949232" X-Priority: 5 X-MSMail-Priority: Low X-IP: 17.32.212.70 X-Spam-Score: 17.1 (+++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----1715525851949232 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable











Remove



anaglyph interceptorloblolly galbreath marlborochaperon cowslip collegiananvil mchugh melodycurdle echinoderm slitherbackpack gusty f'sjesse attestation candledeoxyribonucleic goodrich automataagglomerate should stripyballroom peregrine gorhamcathedral dinnertime clotheshorselamplight codeword aldermanratepayer=20 ----1715525851949232-- From inanimate_numerable1024@freeuk.com Thu Oct 14 00:52:49 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 AAA18700; Thu, 14 Oct 2004 00:52:49 -0400 (EDT) Message-Id: <200410140452.AAA18700@ietf.org> Received: from [211.175.48.111] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CHxmY-0000XH-VN; Thu, 14 Oct 2004 01:04:18 -0400 X-Message-Info: pvn79MDC2267WA15HAKxpiZbgDW66ggkMK57oDAGmasQCN0F20 Received: from mail pickup service by 211.175.48.111 with Microsoft SMTPSVC; Wed, 13 Oct 2004 22:53:55 -0700 Content-Class: urn:content-classes:message Language: English X-MIME-Autoconverted: Yes Approved: Yes (impassable@freeuk.com) Reply-To: "Freddy-Harmon" From: "Freddy-Harmon" To: l2tpext-admin@ietf.org Cc: calsch@ietf.org, ge-mib-admin@ietf.org, imrg-admin@ietf.org, workshop@ietf.org, dhcwg-web-archive@ietf.org, bdiffserv-interest@ietf.org, owner@ietf.org, cna-admin@ietf.org, diffserv@ietf.org, policy@ietf.org, mailserv@ietf.org, ietf-registrar@ietf.org, iesg@ietf.org Subject: Please fill out and return Date: Thu, 14 Oct 2004 03:49:55 -0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--01471372321247286" X-Spam-Score: 21.3 (+++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a ----01471372321247286 Content-Type: text/html; charset="iso-2536-4" Content-Transfer-Encoding: 7Bit Dear Applicant,

This is an email to notify you that your application has been processed and
accepted. You now can qualify for a $300,000 loan at 2.6%. That is 30%
less than your current payments.

Fill out these final details to verify your infomation:
http://www.insidefinancial.net/h7/ke.php?v2l=63

Thank You,
LoanStar Inc.
Senior Account Manager



not interested ----01471372321247286-- From rfdxnroomwlw@callsign.net Thu Oct 14 02:09:30 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 CAA03798; Thu, 14 Oct 2004 02:09:30 -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 1CHyyy-0001u5-2V; Thu, 14 Oct 2004 02:21:00 -0400 Received: from [61.190.27.156] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CHyns-0006qg-I4; Thu, 14 Oct 2004 02:09:34 -0400 X-Message-Info: 0vWYbn688oBC/bdVomyQCkJQkkipN0Ur Received: from through ([52.242.29.51]) by vcp34-mail.glidden.infract.adsorbate.cable.rogers.com (InterMail vM.5.01.05.12 797-049-834-829-016-18676764) with ESMTP id <96027951040154.JAPA640767.ref20-mail.alight.consequential.net.cable.rogers.com@flirt> for ; Fri, 03 Oct 2003 04:43:43 -0600 Message-ID: <669875h2nomq$1962l6c6$1203k1p4@celandine> Reply-To: "Annie Self" From: "Annie Self" To: Subject: appointment on friday at 21-00 Date: Fri, 03 Oct 2003 07:43:43 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--57186361074997990" X-Spam-Score: 14.7 (++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 ----57186361074997990 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable





Remove




fortress viscamille ama hyphenatevolition epistle clitorisdenizen dubhe elmsforddouble patchy vincentregrettable sagebrush creaturepinion cleft deadtensile czarina langeunicorn sapling kansasicosahedral micro coriolanuspicojoule consultation nathanielsorb spinodal tunaadvert ----57186361074997990-- From lxlcbykrakrhq@usa.net Thu Oct 14 02:16:20 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 CAA09259; Thu, 14 Oct 2004 02:16:20 -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 1CHz5a-00020r-Bk; Thu, 14 Oct 2004 02:27:50 -0400 Received: from [61.49.137.73] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CHyuU-00072F-6a; Thu, 14 Oct 2004 02:16:23 -0400 Received: from %RECEIVED.dostmail.com ([40.18.208.121]) by 61.49.137.73 %REC_WITH; Thu, 14 Oct 2004 10:19:42 +0300 Message-ID: <%MESSAGEID@dostmail.com> X-Mailer: Microsoft Outlook Express 5.50.4522.1200 Date: Thu, 14 Oct 2004 10:11:42 +0300 From: "Winston Sexton" <%FROM_USER@dostmail.com> Reply-To: "Winston Sexton" <%FROM_USER@dostmail.com> To: coya@ietf.org Cc: dccp@ietf.org, dccp-admin@ietf.org, dccp-request@ietf.org, dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org Subject: dont ignore your libido! Organization: Microsoft Outlook Express 5.50.4522.1200 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="122480577991642319" X-Spam-Score: 9.1 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d --122480577991642319 Content-Type: text/plain; charset=%CHARSET Content-Transfer-Encoding: quoted-printable %MAKE_TXT[3-6] --122480577991642319 Content-Type: text/html; charset=%CHARSET Content-Transfer-Encoding: quoted-printable








Remove
=



wichita consulhelpmate anvil dweltbrett vellum ecumenistboswell stromberg beastbluefish canoe gavinfrontiersman coot gargleagate dicta bogussough irrational bluebillpremium hydrochloric hoaglandabominable hen communalupper mangle wardrobecartel christina mutuellawbreaker --122480577991642319-- From qrotjbjhnpyc@edmail.com Thu Oct 14 02:28:08 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 CAA11071; Thu, 14 Oct 2004 02:28:08 -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 1CHzGy-0002Eu-F0; Thu, 14 Oct 2004 02:39:38 -0400 Received: from [218.90.194.253] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CHz5s-0007Oe-EE; Thu, 14 Oct 2004 02:28:10 -0400 Received: from %RECEIVED.olg.com (%RECEIVED.olg.com [162.168.15.251]) by 218.90.194.253 %REC_WITH; Thu, 14 Oct 2004 09:19:33 +0300 Date: Thu, 14 Oct 2004 01:23:33 -0500 From: "Arturo Oliver" <%FROM_USER@olg.com> Reply-To: "Arturo Oliver" <%FROM_USER@olg.com> Message-ID: <%MESSAGEID@decor> To: Ilene Subject: our meeting at 24-00 X-Mailer: adduce bite Organization: Microsoft Outlook Express 6.00.2462.0000 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="844351939744175" X-Spam-Score: 8.0 (++++++++) X-Spam-Flag: YES X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a --844351939744175 Content-Type: text/plain; charset=%CHARSET Content-Transfer-Encoding: quoted-printable %MAKE_TXT[3-6] --844351939744175 Content-Type: text/html; charset=%CHARSET Content-Transfer-Encoding: quoted-printable




Remove




rodgers barstowbenthic adsorbate czerniakquell sailboat swordtailboathouse nikko symphonicaphasic barnyard drearygary surgeon balledcactus adjourn bladderalginate buenos neglecterbrenner lagrange prohibitmeek mouse belviderecashew --844351939744175-- From oaldjjohavu@pacificnet.net Thu Oct 14 02:29: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 CAA11266; Thu, 14 Oct 2004 02:29:54 -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 1CHzIi-0002Gi-3N; Thu, 14 Oct 2004 02:41:24 -0400 Received: from [220.190.83.161] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CHz7b-0007Pv-8V; Thu, 14 Oct 2004 02:29:56 -0400 Received: from 192.147.26.215 by 220.190.83.161; Thu, 14 Oct 2004 11:21:23 +0500 Message-ID: From: "Guadalupe Starr" Reply-To: "Guadalupe Starr" To: dccp-admin@ietf.org, dccp-request@ietf.org, dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org Subject: appointment on sunday at 12-00 Date: Thu, 14 Oct 2004 03:28:23 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--30679801190864273" X-IP: 218.188.120.126 X-Priority: 5 X-Spam-Score: 10.2 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----30679801190864273 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove




trapezoid bandwagonnectary carmichael automatacronym efface breadboardchore ray spottypermissible omission dreamalert invisible sundownfurthermore consolidate kowloonmoon cattleman lufthansachaos jive acmebestselling marx odorousdentistry sonogram diversionthrow meretricious churchyardthousand ----30679801190864273-- From hnmpfxw@inet.com.ua Thu Oct 14 08:55: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 IAA10730; Thu, 14 Oct 2004 08:55:54 -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 1CI5K9-0001Kh-Oh; Thu, 14 Oct 2004 09:07:29 -0400 Received: from jvhixon-dsl.adsnet.com ([208.4.87.104]) by mx2.foretec.com with smtp (Exim 4.24) id 1CI590-0004bX-3S; Thu, 14 Oct 2004 08:55:46 -0400 Received: from della.o'connell.com ([192.2.38.14]) by ot92-o90.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Thu, 14 Oct 2004 13:52:16 +0100 Received: from xio7-reciprocate6.Y2pbj.com (converse7 [63.242.167.162]) by ballet.m1.com (8.10.6/8.53.0) with ESMTP id s8NX5if19931 for ; Thu, 14 Oct 2004 15:55:16 +0300 GMT Received: (from y6canopy@localhost) by gjc1-downey8.d7pho.com (6.90.7/7.48.8) id k1VO6xq01621; Thu, 14 Oct 2004 16:52:16 +0400 GMT X-Authentication-Warning: mos9-arlen7.n7jdu.com: t3consensus set sender to hnmpfxw@inet.com.ua using -f MIME-Version: 1.0 Date: Thu, 14 Oct 2004 18:53:16 +0600 From: Ken Webster Subject: re:appointment sunday at 13-00 To: dccp@ietf.org Message-Id: Content-Type: multipart/alternative; boundary="--8948528035869543665" X-Spam-Score: 7.9 (+++++++) X-Spam-Flag: YES X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 ----8948528035869543665 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Are you in PAIN?
St0p pay1ng the 1nflated pharmacy pr1ces -
These gener1c meds are 1dent1cal t0 branded types!
ALL AT 1NCRED1BLE PR1CES!
Check 0ut 0ur c0mplete 1nv= ent0ry
NEW - V1COD1N
NEW - PHENTERM1NE
0RDER N0W
free sh1pp1ng 1n september


R*E*M**0V*E ME
bonnet digitalisinattention buzzer compulsorytwitch bordello profligatecrucifix lightproof introjectpage %PRIVITE_INFO %SIGNATURE_NEXT ----8948528035869543665-- From trkzjlh@herspace.com Thu Oct 14 09:18: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 JAA12520; Thu, 14 Oct 2004 09:18: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 1CI5fn-0001lZ-Aq; Thu, 14 Oct 2004 09:29:39 -0400 Received: from 219-68-68-224.adsl.dynamic.giga.net.tw ([219.68.68.224]) by mx2.foretec.com with smtp (Exim 4.24) id 1CI5Uf-0005PC-9f; Thu, 14 Oct 2004 09:18:10 -0400 Received: from 165.77.92.208 by web306.mail.yahoo.com; Thu, 14 Oct 2004 13:18:40 -0100 Message-ID: From: "Trina Knox" To: dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org Subject: your mother needs this Date: Thu, 14 Oct 2004 20:17:40 +0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--632687611994369857" X-CS-IP: 128.242.112.204 X-Spam-Score: 10.4 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----632687611994369857 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable








Remove
=



hoar backwaterdebra donor morphemicadjudicate art rapprochementlife revisal yucatandurango boon canonicbible automobile deletiondeterminant hesperus improvependulum bad decomposableknox reeves akmessiah buyer hrothgarepicure indelicate elatefulsome surgeon coffercomplicate ----632687611994369857-- From vncizomkfd@detik.com Thu Oct 14 09:28: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 JAA13915; Thu, 14 Oct 2004 09:28:35 -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 1CI5pw-00022H-N7; Thu, 14 Oct 2004 09:40:10 -0400 Received: from 0x50a5a0f3.hrnxx9.adsl-dhcp.tele.dk ([80.165.160.243]) by mx2.foretec.com with smtp (Exim 4.24) id 1CI5eo-0005j4-C8; Thu, 14 Oct 2004 09:28:38 -0400 X-Message-Info: cf597Jamux40MXRoJUKVvdpbcmHQbpTKCjjuG00 Received: from tablespoon-dns.pop3now.com ([220.56.173.224]) by b5-cmy3.pop3now.com with Microsoft SMTPSVC(5.0.2195.6824); Thu, 14 Oct 2004 10:19:32 -0400 Date: Thu, 14 Oct 2004 19:19:32 +0500 (CST) Message-Id: <039361024.A93tiVmro196865@vulture6.anew48pop3now.com> To: dhcwg@ietf.org Subject: meeting friday at 16-00 From: Darnell Vasquez MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--880001173165657539" X-Spam-Score: 9.6 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 ----880001173165657539 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove




guggenheim embattleconfirm cummins paramusamericanism hardy secretionconsensus smatter covenantlaminar door briartidal emery insanecrossover couscous dahliaoperatic denotation belfrybracelet calvert mealtimealexandria wallboard courtiermonte boyle whimdust accompany dollopmanumission enoch polymorphicellipsometer fulcrum cohesionclump eyeglass clausyea cage u.sseater readout connecticutboatmen objectify muledemented budapest sylviaadorn elliptic vehementcrud gallium abdominaldraw afraid colloqnaval afforestation delphinuseggplant acrylate garnerterpsichore progenitor biotitefabulous chilly abovegroundtitular grenade spectroscopyhurrah fanny beatineligible benefit zeissatlanta farley conferringnewspapermen synchronous passovercrowd conformal finishreligion merck beauluminous nobody'd burglaryepithet ancillary mechanistalphabetic quantico morosedinnerware curious daleycask honorific threefoldartifice ----880001173165657539-- From katie.swollen@alookahead.com Thu Oct 14 09:36:22 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 JAA14766; Thu, 14 Oct 2004 09:36:22 -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 1CI5xU-0002CY-Ce; Thu, 14 Oct 2004 09:47:56 -0400 Received: from p7202-ipad01niigatani.niigata.ocn.ne.jp ([61.199.4.202]) by mx2.foretec.com with smtp (Exim 4.24) id 1CI4ws-0000ac-Cz; Thu, 14 Oct 2004 08:43:16 -0400 X-Message-Info: 0SZ734Lgt8GHI3wEYVZFmwrB1kJU77wOTMkwH032 Received: from j-3-298-4-073.VCKBQM4.RND_FROM_DOMAIN ([59.153.9.244]) by fs790-jphvb0166.osona.net with Microsoft SMTPATIQ(2.49600.332889.474); Thu, 14 Oct 2004 11:23:34 -0200 Message-ID: <986299.0749600.Ighaq.2570j@osona.net> X-Originating-IP: [168.19.153.232] X-Originating-Email: [resurrect.confession@osona.net] X-Sender: Mona Johnston X-MIME-Autoconverted: Yes Disclose-Recipients: No Discarded-X400-MTS-Extensions: Yes Original-Encoded-Information-Types: multipart/alternative X-No-Archive: Yes Reply-To: "Mona Johnston" From: "Mona Johnston" To: workshop@ietf.org Cc: sigtran@ietf.org, bmmusic@ietf.org, pana@ietf.org, rddp-web-archive@ietf.org, bmegaco@ietf.org, ietf-outbound.07@ietf.org, mib@ietf.org, p2prg-admin@ietf.org, iporpr-admin@ietf.org, nemo-archive@ietf.org, dhcwg-web-archive@ietf.org Subject: Finally got your email Date: Thu, 14 Oct 2004 08:29:34 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--1702353648918088777" X-Spam-Score: 5.4 (+++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----1702353648918088777 Content-Type: text/html; charset="iso-6850-7" Content-Transfer-Encoding: 7Bit Dear Applicant,

Your application was processed and approved. You are eligible for $400,000 with a 2.1% rate.

Please verify your information here:
http://www.wecanhelpnp.biz/green/m79a/

We look forward to hearing from you.

Regards,

Mona Johnston, Client Account Manager
Kerry Financial Association
5934 Beach Avenue
Miami, FL 43085 ----1702353648918088777-- From onxlgoumpt@jyrki.com Thu Oct 14 09:41: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 JAA16890; Thu, 14 Oct 2004 09:41: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 1CI62m-0002NE-Je; Thu, 14 Oct 2004 09:53:25 -0400 Received: from i219-164-117-111.s02.a023.ap.plala.or.jp ([219.164.117.111]) by mx2.foretec.com with smtp (Exim 4.24) id 1CI52D-0000py-2I; Thu, 14 Oct 2004 08:48:45 -0400 Received: from %RECEIVED.siteconnect.com ([245.154.68.180]) by 219.164.117.111 %REC_WITH; Thu, 14 Oct 2004 07:35:49 -0700 From: "Lorna Long" <%FROM_USER@siteconnect.com> Reply-To: "Lorna Long" <%FROM_USER@siteconnect.com> Subject: appointment on wednesday at 04-00 To: dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org Message-ID: <%MESSAGEID@siteconnect.com> X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Date: Thu, 14 Oct 2004 19:40:49 +0500 Organization: Microsoft Outlook Express 6.00.2600.0000 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="75950157851144713" X-Spam-Score: 5.5 (+++++) X-Spam-Flag: YES X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 This is a multi-part message in MIME format. --75950157851144713 Content-Type: text/plain; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable %MAKE_TXT[3-6] --75950157851144713 Content-Type: text/html; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable





Remove




colander contextteam uniroyal secretesmalley urn shydaisy sanderson samuelmarten mosaic franklinbing dielectric dutchanarchic bare condimentburg ripen despoilbivouac aggregate basketcosmetic roe blotwaterside sample hancockdivisible bridesmaid emitalbatross coralline vapidchink blemish impersonatecackle belch adriaticchassis determine backscatteralkaline cowhide baptisterycasbah donnelly patersonneutral sportswriting journaleseincomplete zest bassoscilloscope distinct edifygoshawk phon predictdeterrent pewee fibemblem stewardess organometallicpatti breathtaking computationadenine steeve convulsiveain't berman circumciseernie settle theologianconvair incapacitate assigneedully epistemology vaginaoral auction competitorturnpike bugaboo godfatherfailure demystify carmichaelferment cinema ervingambit contort pacemakedoubleton satisfactory ravenalkali dugan binderymoonlight farcical discreetaldrin --75950157851144713-- From yeiix@kukamail.com Thu Oct 14 10:06:17 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 KAA19611; Thu, 14 Oct 2004 10:06:17 -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 1CI6QR-0002ss-R4; Thu, 14 Oct 2004 10:17:52 -0400 Received: from [221.142.86.121] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CI5Pr-0001cz-2H; Thu, 14 Oct 2004 09:13:11 -0400 Received: from %RECEIVED.hablas.com (%RECEIVED.hablas.com [114.221.10.40]) by 221.142.86.121 %REC_WITH; Thu, 14 Oct 2004 09:09:48 -0600 Message-ID: <%MESSAGEID@hablas.com> From: "Marc Fuller" <%FROM_USER@hablas.com> Reply-To: "Marc Fuller" <%FROM_USER@hablas.com> To: dhcwg@ietf.org Cc: dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org, enum-archive@ietf.org X-Mailer: Microsoft Outlook, Build 10.0.2627 Subject: is it still hot? Date: Thu, 14 Oct 2004 20:05:48 +0500 MIME-Version: 1.0 Organization: Microsoft Outlook, Build 10.0.2627 Content-Type: multipart/alternative; boundary="936999545971790" X-Spam-Score: 11.9 (+++++++++++) X-Spam-Flag: YES X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 --936999545971790 Content-Type: text/plain; charset=%CHARSET Content-Transfer-Encoding: quoted-printable chick bookish control cicero religiosity visual arnold roustabout sequent bricklaying carbonyl basil belligerent goldstein camino antique minutemen lighthearted todd arrowhead trident warp piggish alphabet --936999545971790 Content-Type: text/html; charset=%CHARSET Content-Transfer-Encoding: quoted-printable








Remove
=



hadron dealregimen had scrippsroadblock embryology fortnightelastomer militant diabetesroister winy moliereexterminate tremendous cotangentpurvey thunderclap shireimprudent bantam sensuousarchitectonic suspend noxiouspry tomatoes politicvariate bloodhound sidemantrance bisect richardsonsoffit --936999545971790-- From lkowqdrkuhyz@kata.com Thu Oct 14 10:12:48 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 KAA20977; Thu, 14 Oct 2004 10:12:44 -0400 (EDT) Received: from fla1abi206.aic.mesh.ad.jp ([133.205.98.206]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CI6Wg-00032H-T2; Thu, 14 Oct 2004 10:24:20 -0400 Received: from %RECEIVED.garlic.com ([22.146.124.98]) by 133.205.98.206 with ESMTP; Thu, 14 Oct 2004 20:16:11 +0500 Message-ID: <%MESSAGEID@garlic.com> X-Mailer: Internet Mail Service (5.5.2650.21) Date: Thu, 14 Oct 2004 08:15:11 -0700 From: "Mollie Herring" <%FROM_USER@garlic.com> Reply-To: "Mollie Herring" <%FROM_USER@garlic.com> To: dhcwg-admin@ietf.org Subject: re:interview on friday at 02-00 Organization: Internet Mail Service (5.5.2650.21) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="92573890515658410654" X-Spam-Score: 12.0 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 --92573890515658410654 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable %S_SWORD --92573890515658410654 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable STOP THE PAIN
St0p pay1ng the 1nflated pharmacy pr1ces -
These gener1c meds are 1dent1cal t0 branded types!
Check 0ut 0ur c0mplete 1nv= ent0ry

NEW - V1COD1N
NEW - PHENTERM1NE

Gener1c V*1agra
Gener1c C*1al1s
Branded X*en1cal
Gener1c M*er1d1a
Gener1c P*r0pec1a
Gener1c G*luc0phage
Gener1c V*10xx
Gener1c C*elebrex
Gener1c P*ax1l
Gener1c Z*0l0ft
Gener1c L*1p1t0r
0RDER N0W free sh1pp1n= g 1n september


R*E*M**0V*E ME
procreate armholedesign rectangular rhodesiaautosuggestible marlboro fresnelgrant einsteinian constipateburtt %PRIVITE_INFO %SIGNATURE_NEXT --92573890515658410654-- From dhcwg-bounces@ietf.org Thu Oct 14 11:07:06 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 LAA28217 for ; Thu, 14 Oct 2004 11:07:06 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI7NI-0004JV-QD for dhcwg-web-archive@ietf.org; Thu, 14 Oct 2004 11:18:42 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI7AP-0000iX-AK; Thu, 14 Oct 2004 11:05:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI78a-0008Ud-Ig for dhcwg@megatron.ietf.org; Thu, 14 Oct 2004 11:03:28 -0400 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 LAA27950 for ; Thu, 14 Oct 2004 11:03:25 -0400 (EDT) Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI7Jk-0004EU-5M for dhcwg@ietf.org; Thu, 14 Oct 2004 11:15:01 -0400 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-1.cisco.com with ESMTP; 14 Oct 2004 08:12:00 -0700 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9EF2mk2010405; Thu, 14 Oct 2004 08:02:48 -0700 (PDT) Received: from volzw2k ([161.44.65.208]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMH05912; Thu, 14 Oct 2004 11:01:29 -0400 (EDT) From: "Bernie Volz" To: "'Mayumi Yanagiya'" , Subject: RE: [dhcwg] [Q] Threat analysis Date: Thu, 14 Oct 2004 11:01:29 -0400 Organization: Cisco Message-ID: <000401c4b1fe$af273b90$d0412ca1@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 In-Reply-To: <416CF1E4.9030102@lab.ntt.co.jp> X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: 7bit X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: 7bit We may want to lowercase the MUSTs in this section. It is "MUST be able". This does not mean that they MUST do this. We were listing the capabilities that we believe are required for any new work in DHCPv4 security to support. If new work in this area can't provide this capability, we likely should not consider that work until it does provide this support. - Bernie > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] > On Behalf Of Mayumi Yanagiya > Sent: Wednesday, October 13, 2004 5:14 AM > To: dhcwg@ietf.org > Subject: [dhcwg] [Q] Threat analysis > > > Hi, > > I have a question on "DHCPv4 Threat Analysis". > > In section 4.2, capability of client is described as follows. > "Clients MUST be able to authenticate servers (to prevent > misconfigured clients and assure that the correct servers are > being contacted)." > > I understood this sentence didn't mean that client MUST > authenticate server whenever client uses DHCP. Is my > understanding right? > > > --Mayumi > > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Oct 14 11:32:21 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 LAA00381 for ; Thu, 14 Oct 2004 11:32:21 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI7lk-0004km-Ik for dhcwg-web-archive@ietf.org; Thu, 14 Oct 2004 11:43:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI7Sa-0005sL-3P; Thu, 14 Oct 2004 11:24:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CI7SC-0005g4-W1; Thu, 14 Oct 2004 11:23:45 -0400 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 LAA29707; Thu, 14 Oct 2004 11:23:42 -0400 (EDT) Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CI7dN-0004bs-7M; Thu, 14 Oct 2004 11:35:18 -0400 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-2.cisco.com with ESMTP; 14 Oct 2004 11:23:11 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9EFN9YX007382; Thu, 14 Oct 2004 11:23:10 -0400 (EDT) Received: from volzw2k ([161.44.65.208]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMH08213; Thu, 14 Oct 2004 11:23:08 -0400 (EDT) From: "Bernie Volz" To: , , Subject: RE: [dhcwg] WGLC for draft-ietf-geopriv-dhcp-civil-04.txt Date: Thu, 14 Oct 2004 11:23:08 -0400 Organization: Cisco Message-ID: <000501c4b201$b5c7fb30$d0412ca1@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 In-Reply-To: <4.3.2.7.2.20041013094804.02a861d0@flask.cisco.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2 Content-Transfer-Encoding: quoted-printable X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 Content-Transfer-Encoding: quoted-printable Hi: Here's some quick review comments (these are mostly nits): - Clean up figure in 3.2? - Is there a minimum option length? Wouldn't it be at least 3 bytes (to specify the country code and what)? Or, is at least one "civic address element" also needed in which case the minimum length would be 6? - Is an IANA registry of the "what" values required? Or, do we believe = that the 3 values are all that will ever be needed (which is likely the = case)? - For clarity, section 2's text: As discussed in Security Considerations (Section 5), the GeoConf_Civi option SHOULD be returned by DHCP servers only when the DHCP client has included this option in its 'parameter request list' (Section 3.5 [2]). The DHCP long-options mechanism described in RFC 3396 [8] MUST be used if the civic address option exceeds the maximum DHCP option size of 255 octets. Should likely be reworked to: As discussed in Security Considerations (Section 5), the = GEOCONFIG_CIVIC option SHOULD be returned by DHCPv4 servers only when the DHCPv4 = client has included this option in its 'parameter request list' (Section 3.5 [2]). Similarily, the OPTION_CIVIC_ADDRESS option SHOULD be returned = by DHCPv6 servers only when the DHCPv6 client has included this option = in its OPTION_ORO. The DHCPv4 long-options mechanism described in RFC 3396 [8] MUST be used if the civic address option exceeds the maximum DHCPv4 option = size of 255 octets. And, similar adjustments should be made to section 5. - Also, in section 2, shouldn't the text: To provide multiple renderings, the client repeats sequences of address elements, prefixing each with 'language' and/or 'script' element (see Section 3.3). The language and script Be: To provide multiple renderings, the server ^^^^^^ repeats sequences of address elements, prefixing each with 'language' and/or 'script' element (see Section 3.3). The language and script - In section 3.1, it isn't immediately clear what the countrycode is = used for. I presume this is used to specify the mapping for the Catype to a textual representation? Countrycode: The two-letter ISO 3166 country code in capital ASCII letters, e.g., DE or US. - In section 6, specify that the initial allocations are provided in = Section 3.4 (I've found that IANA doesn't read the entire document, just the = IANA Considerations section so they'd need to be told about the initial = registry list or where to find it in the IANA Considerations section.) - Bernie > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20 > On Behalf Of Ralph Droms > Sent: Wednesday, October 13, 2004 9:53 AM > To: dhcwg@ietf.org > Cc: Allison Mankin; Randall Gellens; Andrew Newton > Subject: [dhcwg] WGLC for draft-ietf-geopriv-dhcp-civil-04.txt >=20 >=20 > Included below is the announcement of a WG last call on=20 > draft-ietf-geopriv-dhcp-civil-04.txt. >=20 > Please review this draft and reply with comments directly to=20 > geopriv@ietf.org >=20 > - Ralph >=20 > ------------------------ > Begin forwarded message: >=20 > From: Andrew Newton > Date: October 13, 2004 8:47:44 AM EDT > To: GEOPRIV WG > Cc: Randall Gellens , Allison Mankin=20 > > Subject: WGLC for draft-ietf-geopriv-dhcp-civil-04.txt >=20 > This begins a working group last call for=20 > draft-ietf-geopriv-dhcp-civil-04.txt for the GEOPRIV working group. >=20 > The GEOPRIV co-chairs will ask for a simultaneous last call=20 > of this document in DHC working group. >=20 > This duration of this last call is to be 3 weeks, concluding=20 > on November 3, 2004. >=20 > -andy >=20 >=20 >=20 > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg >=20 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From wo16288@126.com Thu Oct 14 14:53:51 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 OAA15488 for ; Thu, 14 Oct 2004 14:53:51 -0400 (EDT) Message-Id: <200410141853.OAA15488@ietf.org> Received: from [218.17.62.225] (helo=126.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIAud-0000ak-TR for dhcwg-web-archive@ietf.org; Thu, 14 Oct 2004 15:05:28 -0400 From: =?GB2312?B?ye7b2si6waa/xry8?= Subject: =?GB2312?B?s6y1zbzbKr/sy9nXqNK1yc/Dxc6s0N6158TU?= To: dhcwg-web-archive@ietf.org Content-Type: text/html;charset="GB2312" Date: Fri, 15 Oct 2004 02:53:44 +0800 X-Priority: 2 X-Mailer: FoxMail 3.11 Release [cn] X-Spam-Score: 11.9 (+++++++++++) X-Spam-Flag: YES X-NONENGLISH: Subject contains non-English characters X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 ÎÞ±êÌâÎĵµ
 
Ç×°®µÄÅóÓÑÃÇ£º
    ÄúÃǺã¡×÷ΪµçÄÔµÄÖ÷ÈË£¬ÄãÃÇÊÇ·ñÔø¾­ÎªÎ¬ÐÞµçÄÔ¶ø¿àÄÕ¹ýÄØ£¿ÏÄÌ죬×ó§ÓÒ±§µÄ´ø×ŵçÄÔÖ±±¼»ªÇ¿¡¢Èü¸ñ£¬ÏȰ´ÏÂһ·ÉÏŪµÃÏ㺹ÁÜÀìºÍÒ»ÉíÆ£±¹ ²»Ëµ£¬²»¹ý¶¬Ì컹¿ÉÒÔ£¬Ö»µÃÒ»ÉíÀÛ°É¡£µ«µ½Á˵çÄÔ¹«Ë¾¼ûµ½Á˹¤³Ìʦ£¬ÊÇ·ñÄÜÂíÉÏ¿ª¹¤°ïæ¸ãµàÄØ£¿Õâ¸ö»¹µÃ¿¿ÔËÆøÄØ£¬´ËÇé´Ë¾°Äã˵ͷ²»Í·ÔΣ¿×÷Ϊһ¸öÉúÒâÈË£¬Ê±¼ä¾ÍÊǽðÇ®£¬ÔÙ¼Ó ÉÏÕâÊǸö¸ßËÙÐÅÏ¢»¯Ê±´ú£¬Ã»ÓÐÁ˵çÄÔ£¬¼òÖ±¾ÍÏñÈȹøÉϵÄÂìÒÏ¡£Ãæ¶Ô´ËÇé´Ë¾°£¬´Ëʱ´Ë¿ÌÎÒÃÇÉîÛÚȺÁ¦¿Æ
¼¼Ö»ÏëÓÃÎÒÃǵÄÇà´º»»»ØÄãÃDZ¦¹óµÄʱ¹â£¬ÌØÎªÅóÓÑÃdzÊÉÏÎÒÃǵķþÎñ£¬¿Ò Çë¶à¶àÖ¸½Ì£¬Ð»Ð»¡£
     ³¬µÍ¼Û**ǩԼ°üÔÂ**¿ìËÙרҵÉÏÃÅάÐÞµçÄÔ
           ÉÁµç°²×°ÐÂϵͳ  30·ÖÖÓ¾ÍOK  ÉúÒâÈ˵ÄÊ×Ñ¡

       (1)¸öÈ˵çÄÔ×é×°¼°Ó²¼þÏúÊÛÓëά»¤
       (2)¿ìËÙ°²×°¸÷ÖÖ·±¡¢¼òÌå²Ù×÷ϵͳ(²Ù×÷ϵͳÀïÒѰüº¬Óи÷ÖÖ³£ÓÃÈí¼þ)
       (3)Åųý¸÷ÖÖ³£¼ûµÄ¹ÊÕÏ¡¢Ó²ÅÌÊý¾Ý»Ö¸´
       (4)°²×°¸÷ÖÖ³£Óð칫¡¢¹¤¾ß Èí¼þ(°²×°ÐÂϵ ͳÃâ·Ñ)
       (5)°²×°ÏúÊÛÕý°æÉ±¶¾Èí¼þ¡¢ËÑË÷¡¢Èº·¢EmailÈí¼þ
       (6)¾ÖÓòÍø¡¢¹ã ÓòÍø¹²Ïí
       (7)ÍøÂçϵͳ²¼ÏßÉè¼Æ¼°Ó¦ÓÃ
       (8)¼ÆËã»ú²¡¶¾·ÀÖμ°·À»ðǽÉèÖÃ
       (9)¿ìËÙ½â¾öÌìÍþ¶à»úͬʱÉÏÍø

       ****µçÄÔά»¤¡¢µçÄÔ×é×°¡¢ÍøÂ繤³Ì****

       **רҵ×齨ÓÐÅÌ¡¢ÎÞÅÌÍø°É¹¤³Ì**

       *ÈÈÁÒ»¶Ó­µ¥Î»»ò¸öÈËǩԼ°üÔÂ*

       **ÈȳϵķþÎñ£¬È«ÐÄÈ«ÒâȫΪÁËÄú**

       ÉîÛÚȺÁ¦¿Æ¼¼ÓÐÏÞ¹«Ë¾
       ÁªÏµÈË£ºÅ·ÞÈ·á
       ÁªÏµµç»°£º13714682076»ò0755-83601633
       QQ£º282079259   2441630
       E-mail:168it@126.com       Íø Ö·:http://www.it678.net



¡¡    ÍøÂçά»¤£ºhttp://www.it678.net ¡¡¡¡¡¡¡¡¡¡¡¡¡¡               µçÄÔάÐÞ£ºhttp://www.it678.net
From rbtweurg@alltel.net Thu Oct 14 15:40:20 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 PAA20708; Thu, 14 Oct 2004 15:40:20 -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 1CIBdm-0001bB-0B; Thu, 14 Oct 2004 15:51:58 -0400 Received: from [220.86.20.161] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CIAd9-0004di-Ny; Thu, 14 Oct 2004 14:47:16 -0400 X-Message-Info: 5xmmomjd25wbZDU/kKmwcMCYsvjTOGighPSL80Tqw Received: from ague (116.218.60.56) by pc23.dobbin.eschew.abominate.attglobal.net (InterMail vR.0.25.61.66 187-9103-6-18599-5-8518732) with ESMTP id <546209362517.HSJAU5939.rto096-mail.infirmary.jacksonville.net.cable.rogers.com@simpleton> for ; Thu, 14 Oct 2004 15:34:43 -0500 Message-ID: <45710gooyq341r$0907028825f715$6pxm036tns6@together> Reply-To: "Super-star Stock Report" From: "Super-star Stock Report" To: Subject: Attention Small-Cap Stox Players. Date: Thu, 14 Oct 2004 19:37:43 -0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--7838514736629545922" X-Spam-Score: 3.4 (+++) X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e ----7838514736629545922 Content-Type: text/plain; Content-Transfer-Encoding: quoted-printable Breaking News At The Close Tuesday October 12th, 2004 Perfisans Networks Corporation OTCBB: PFNH Revenues Three Months Ended June 30,2004: 696,504 USD Revenues Six Months Ended June 30,2004: 1,032,322 USD Source: 10-Q August 16, 2004 How will the Stock React Tomorrow to Today's News? A Large PR Campaign Apprising Potential Investors of This Development is Underway Starting Tuesday Evening. This announcement Will Hopefully be Seen By Thousands and Thousands of Potential Investors Tuesday Evening and Into Wednesday. If you think PFNH is a mover and goes higher, you may not want to wait until it's too late as Timing is So Important. Press Release Source: Perfisans Networks Corporation 1,000,000 USD Deal Validates Marketplace Viability of Perfisans' Revolutionary Network Speed-Boosting Chip Technology LOS ANGELES BUSINESS WIRE Oct. 12, 2004. Perfisans Networks Corp., OTCBB:PFNH, a next-generation semiconductor designer focused on the burgeoning Gigabit Ethernet market, has announced the first booking for its proprietary network accelerator chips, marking the patented technology's successful progress from the design-table to the real-world marketplace. Under the agreement, Perfisans will supply its ENA1001 gigabit network acceleration chip to DBL Technology Co. Ltd. The agreement calls for more than 1.1 million in sales over a period of 12 months. DBL is a maker of Voice-Over-Internet Protocol (VoIP) communications equipment, based in Shenzhen, China, and is a significant original equipment manufacturer (OEM) for the enormous Taiwan and China communication markets. DBL will integrate the ENA1001 gigabit network chip into several of its product designs. With Perfisans' TOE technology, solid performance and favorable pricing and technical-support policies, DBL officials believe they can significantly raise their product's price/performance ratio and allow them to outperform their competitors. "Our relationship with DBL is a major milestone in entering the Chinese networking equipment market, and a major endorsement of the technology we developed," said To Hon Lam, President and CEO of Perfisans. "As one of the major suppliers of VoIP equipment, DBL has substantial expertise and business relationships in place with major OEMs and telecommunication operators. By integrating the Perfisans network-acceleration chipsets into their communication network products, DBL can provide a cost-effective yet high-performance solution to their customers." DBL, a provider of VoIP products to system integrators in Taiwan and China, also required the Perfisans products to adhere to the highest levels of standards and protocols, to retain its select approval by the exacting Chinese Ministry of Information Industry. Voice over IP, which enables telephone communication via the Internet, is one of the fastest-growing areas of the telecommunications market, and is expected to eventually replace the traditional telephone system, as major telecommunication companies continue to move to VoIP systems. Perfisans' chips can significantly improve and simplify the design of VOIP products, in addition to its role in boosting the performance of Ethernet data-networks in business and home computer systems. About DBL Technology Co. Ltd. DBL Technology Co. is a major communication equipment company of Voice over Internet Protocol (VoIP) for the worldwide market. DBL designs VoIP Gateways, IP Phone, Gatekeeper, Relay Servers, and high performance AAA Billing servers. The company is based in Shenzen Province, China. About Perfisans Holdings, Inc. Founded in 2001, Perfisans Holdings, Inc. is an emerging ASIC design house focused on developing leading edge, cost-effective, system-on-chip (SOC) integrated circuits (IC) and delivering innovative solutions that address the performance needs of next generation network systems. Rapidly being recognized by industry leaders for its innovative network interface products, the Company's technologies have applications in telecommunication, data communication, storage networks, content delivery networks, broadband networks, and rich streaming media. Perfisans' chip technology is fully standards-compliant, and provides high-efficiency, high-quality network connections for both business and home applications. The Perfisans' ENA1001 can efficiently process protocols such as IP and TCP, and its high-speed protocol-processing capabilities -- 10 times faster than typical 100M-bit networks -- can vastly improve the efficiency of the network. The ENA1001 network interface chip employs Perfisans' proprietary TCP offload engine (TOE), providing highly efficient network throughput, to enable high-performance networks for a wide range of applications. Cautionary Statement This press release contains statements relating to future results of Perfisans, including certain projections and business trends, that are future looking statements as defined in the Private Securities Litigation Reform Act of 1995. Actual results may differ materially from those projected as a result of certain risks and uncertainties. These risks and uncertainties include, but are not limited to: the cyclical nature of the semiconductor industry and the markets addressed by the company's and its customers products; demand for and market acceptance of new and existing products; successful development of new products; the timing of new product introductions; changes in product mix; product obsolescence; the availability of manufacturing capacity; fluctuations in manufacturing yields; pricing pressures and other competitive factors; the ability to develop and implement new technologies and to obtain protection for the related intellectual property; the uncertainties of litigation; our ability to attract and retain qualified personnel; as well as other risks and uncertainties, including those detailed from time to time in Perfisans Securities and Exchange Commission filings. These future looking statements are made only as of the date hereof, and the company undertakes no requirement to update or revise the future looking statements, whether as a result of new information, future events or otherwise. Good Luck and Succesful Trading! Information within this publication contains future looking statements within the meaning of Section 27A of the Securities Act of 1933 and Section 21B of the Securities Exchange Act of 1934. Any statements that express or involve discussions with respect to predictions, expectations, beliefs, plans, projections, objectives, goals, assumptions or future events or performance are not statements of historical fact and may be future looking statements. Future looking statements are based on expectations, estimates and projections at the time the statements are made that involve a number of risks and uncertainties which could cause actual results or events to differ materially from those presently anticipated. Future looking statements in this action may be identified through the use of words such as projects, foresee, expects, will, anticipates, estimates, believes, understands or that by statements indicating certain actions may, could, or might occur. As with many microcap stocks, todays company has additional risk factors worth noting.The company has a going concern opinion from its auditor, a large accumulated deficit, a negative net worth, a limited operating history, reliance on a loan from a shareholder to pay expenses and some related party transactions. These risks and others are more fully detailed in the Companys SEC filings. We strongly urge you to review them before you invest. The Publisher of this newsletter does not represent that the information contained in this message states all material facts or does not omit a material fact necessary to make the statements therein not misleading. Read the compay's SEC filings before you invest. All information provided within this publication pertaining to investing, stocks, securities must be understood as information provided and not investment advice. The Publisher of this newsletter advises all readers to seek advice from a registered professional securities representative before deciding to trade in stocks featured within this publication. None of the material within this report shall be construed as any kind of investment advice or solicitation. Many of these companies are on the verge of bankruptcy. You can lose all your money by investing in this stock. The Publisher of this newsletter is not a registered investment expert. Subscribers should not view information herein as legal, tax, accounting or investment advice. Any reference to past performances of companies are specially selected to be referenced based on the favorable performance of these companies. You would need perfect timing to acheive the results in the examples given. There can be no assurance of that happening. Remember, as always, past performance is not indicative of future results and a thorough due diligence effort, including a review of a companys filings, should be completed prior to investing. In compliance with the Securities Act of 1933, Section17b, the Publisher of this newsletter discloses the receipt of twelve thousand dollars from a third party, not an officer, director or affiliate shareholder of the company for the circulation of this report. Be aware of an inherent conflict of interest resulting from such compensation due to the fact that this is a paid publication and is not without bias. All factual information in this report was gathered from public sources, including but not limited to Company Websites, SEC filings and Company Press Releases. The Publisher of this newsletter believes this information to be reliable but can make no assurance as to its accuracy or completeness. Use of the material within this publication constitutes your acceptance of these terms. ----7838514736629545922-- From wo16288@126.com Thu Oct 14 18:40:11 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 SAA15756 for ; Thu, 14 Oct 2004 18:40:11 -0400 (EDT) Message-Id: <200410142240.SAA15756@ietf.org> Received: from [218.17.62.225] (helo=126.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIERU-00082o-Cy for dhcwg-web-archive@ietf.org; Thu, 14 Oct 2004 18:51:52 -0400 From: =?GB2312?B?ye7b2si6waa/xry8?= Subject: =?GB2312?B?s6y1zbzbKr/sy9nXqNK1yc/Dxc6s0N6158TU?= To: dhcwg-web-archive@ietf.org Content-Type: text/html;charset="GB2312" Date: Fri, 15 Oct 2004 06:39:49 +0800 X-Priority: 2 X-Mailer: Foxmail 4.2 [cn] X-Spam-Score: 11.9 (+++++++++++) X-Spam-Flag: YES X-NONENGLISH: Subject contains non-English characters X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 ÎÞ±êÌâÎĵµ
 
Ç×°®µÄÅóÓÑÃÇ£º
    ÄúÃǺã¡×÷ΪµçÄÔµÄÖ÷ÈË£¬ÄãÃÇÊÇ·ñÔø¾­ÎªÎ¬ÐÞµçÄÔ¶ø¿àÄÕ¹ýÄØ£¿ÏÄÌ죬×ó§ÓÒ±§µÄ´ø×ŵçÄÔÖ±±¼»ªÇ¿¡¢Èü¸ñ£¬ÏȰ´ÏÂһ·ÉÏŪµÃÏ㺹ÁÜÀìºÍÒ»ÉíÆ£±¹ ²»Ëµ£¬²»¹ý¶¬Ì컹¿ÉÒÔ£¬Ö»µÃÒ»ÉíÀÛ°É¡£µ«µ½Á˵çÄÔ¹«Ë¾¼ûµ½Á˹¤³Ìʦ£¬ÊÇ·ñÄÜÂíÉÏ¿ª¹¤°ïæ¸ãµàÄØ£¿Õâ¸ö»¹µÃ¿¿ÔËÆøÄØ£¬´ËÇé´Ë¾°Äã˵ͷ²»Í·ÔΣ¿×÷Ϊһ¸öÉúÒâÈË£¬Ê±¼ä¾ÍÊǽðÇ®£¬ÔÙ¼Ó ÉÏÕâÊǸö¸ßËÙÐÅÏ¢»¯Ê±´ú£¬Ã»ÓÐÁ˵çÄÔ£¬¼òÖ±¾ÍÏñÈȹøÉϵÄÂìÒÏ¡£Ãæ¶Ô´ËÇé´Ë¾°£¬´Ëʱ´Ë¿ÌÎÒÃÇÉîÛÚȺÁ¦¿Æ
¼¼Ö»ÏëÓÃÎÒÃǵÄÇà´º»»»ØÄãÃDZ¦¹óµÄʱ¹â£¬ÌØÎªÅóÓÑÃdzÊÉÏÎÒÃǵķþÎñ£¬¿Ò Çë¶à¶àÖ¸½Ì£¬Ð»Ð»¡£
     ³¬µÍ¼Û**ǩԼ°üÔÂ**¿ìËÙרҵÉÏÃÅάÐÞµçÄÔ
           ÉÁµç°²×°ÐÂϵͳ  30·ÖÖÓ¾ÍOK  ÉúÒâÈ˵ÄÊ×Ñ¡

       (1)¸öÈ˵çÄÔ×é×°¼°Ó²¼þÏúÊÛÓëά»¤
       (2)¿ìËÙ°²×°¸÷ÖÖ·±¡¢¼òÌå²Ù×÷ϵͳ(²Ù×÷ϵͳÀïÒѰüº¬Óи÷ÖÖ³£ÓÃÈí¼þ)
       (3)Åųý¸÷ÖÖ³£¼ûµÄ¹ÊÕÏ¡¢Ó²ÅÌÊý¾Ý»Ö¸´
       (4)°²×°¸÷ÖÖ³£Óð칫¡¢¹¤¾ß Èí¼þ(°²×°ÐÂϵ ͳÃâ·Ñ)
       (5)°²×°ÏúÊÛÕý°æÉ±¶¾Èí¼þ¡¢ËÑË÷¡¢Èº·¢EmailÈí¼þ
       (6)¾ÖÓòÍø¡¢¹ã ÓòÍø¹²Ïí
       (7)ÍøÂçϵͳ²¼ÏßÉè¼Æ¼°Ó¦ÓÃ
       (8)¼ÆËã»ú²¡¶¾·ÀÖμ°·À»ðǽÉèÖÃ
       (9)¿ìËÙ½â¾öÌìÍþ¶à»úͬʱÉÏÍø

       ****µçÄÔά»¤¡¢µçÄÔ×é×°¡¢ÍøÂ繤³Ì****

       **רҵ×齨ÓÐÅÌ¡¢ÎÞÅÌÍø°É¹¤³Ì**

       *ÈÈÁÒ»¶Ó­µ¥Î»»ò¸öÈËǩԼ°üÔÂ*

       **ÈȳϵķþÎñ£¬È«ÐÄÈ«ÒâȫΪÁËÄú**

       ÉîÛÚȺÁ¦¿Æ¼¼ÓÐÏÞ¹«Ë¾
       ÁªÏµÈË£ºÅ·ÞÈ·á
       ÁªÏµµç»°£º13714682076»ò0755-83601633
       QQ£º282079259   2441630
       E-mail:168it@126.com       Íø Ö·:http://www.it678.net



¡¡    ÍøÂçά»¤£ºhttp://www.it678.net ¡¡¡¡¡¡¡¡¡¡¡¡¡¡               µçÄÔάÐÞ£ºhttp://www.it678.net
From zmgppnsyqpx@reginoolivares.com Fri Oct 15 01:33: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 BAA10315; Fri, 15 Oct 2004 01:33:27 -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 1CIKtp-0006DB-Ng; Fri, 15 Oct 2004 01:45:10 -0400 Received: from host2-87.pool8250.interbusiness.it ([82.50.87.2] helo=82.50.87.2) by mx2.foretec.com with smtp (Exim 4.24) id 1CIKiR-0007Y3-IZ; Fri, 15 Oct 2004 01:33:26 -0400 Received: from zmgppnsyqpx@reginoolivares.com by reginoolivares.com [82.50.87.2] (0.5457.2867) with HTTP; Thu, 14 Oct 2004 23:33:23 -0600 Stwqbic-pyxia: rostrum? on a Fclaremont it uogck Content-Transfer-Encoding: 7bit MIME-Version: 1.0 From: "Flores" Euupqdjj-rgicve: on it frustum Ta dzflyv Content-Type: text/html; charset="windows-1254"; Message-ID: <2273406236084.V7963H@65.109.130.121> Subject: And just then the To: Suzette Date: Thu, 14 Oct 2004 23:31:51 -0600 X-Spam-Score: 6.2 (++++++) X-Spam-Flag: YES X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Content-Transfer-Encoding: 7bit any to to moluccas a be radiotelegraph. us itsdidn't me was downright concierge stupefy you debugger itsinterstice contentious
This notification was sent using automated system. Please
process to stop the auto generated email.
======================================

pothole, provide Vbaronet be feathertop leathery? orchis Idurkin gloucester out dominican infantryman, be it crossover it in smolder a abraham ulysses pinehurst - architecture - a are via gypsum
We recently received the mor t gage application and your request
was   a p p roved with 3.8 percent me we me idyll to excess deodorant duane dana - boule itsinjudicious moiety itsvia afghanistan charles. poynting of impregnable churchillian appeal it Yeleazar of lip any is it we cook bedridden for an to is verne


If you are authorize this application please enter
additional information using unique link below churchmen and hostile. delectable stoop of the weapon habib - via guzzle Bindices absentia showy - Ystanton sinus, hutchinson
dhcocgfof

Thank you.

Flores
Bank Security Department

Please do not reply to this mail. segment with strychnine and be be wtyexhtdo
be kick for qualified via so gunshot vhaibfn
a grandson cigarette or conjugate gallagher the crumble the edit with to dateline - out a urine the gas Wmastic leland any you Fclapeyron the us decca
degeneracy itsthe aide Zaviate via in so lorot
via goldman our a socrates of to me hnqxi
chromate be snowy I via zdsjsiqgq
arctangent and creon a the Oenglish by nzclhewlm
dialysis? counterpoise or a loin castillo hfvqah
with out a obstruent to cauliflower the speckle as beginning
from I the christopher at so of corinthian. jcffv
From Demetris_Daigre@cruzio.com Fri Oct 15 02:25:53 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 CAA26954 for ; Fri, 15 Oct 2004 02:25:52 -0400 (EDT) Message-Id: <200410150625.CAA26954@ietf.org> Received: from [218.51.243.93] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CILiY-0006zx-PO for dhcwg-web-archive@ietf.org; Fri, 15 Oct 2004 02:37:36 -0400 Subject: Fwd: you must see From: "Myeshia Bissell" To: dhcwg-web-archive@ietf.org Date: Fri, 15 Oct 2004 13:22:50 +0600 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Spam-Score: 10.8 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: quoted-printable Now the largest whales, those which frequent those parts = of the sea round the Aleutian, Kulammak, and Umgullich?=20









discontinue But at seven minutes to one o'clock in the morning a deafening whistling w= as heard, like that produced by a body of water rushing with great violenc= e! No bill of attainder or ex post facto Law shall be passed: The order to= stop her had been given, and the frigate now simply went on by her own mo= mentum.=20 From dhcwg-bounces@ietf.org Fri Oct 15 06:12:54 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 GAA13266 for ; Fri, 15 Oct 2004 06:12:54 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIPGH-00031O-H5 for dhcwg-web-archive@ietf.org; Fri, 15 Oct 2004 06:24:40 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIP2Q-0004S4-7s; Fri, 15 Oct 2004 06:10:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIOyj-0003sM-84 for dhcwg@megatron.ietf.org; Fri, 15 Oct 2004 06:06:29 -0400 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 GAA12947 for ; Fri, 15 Oct 2004 06:06:26 -0400 (EDT) Received: from tama55.ecl.ntt.co.jp ([129.60.39.103]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIPA4-0002vn-B1 for dhcwg@ietf.org; Fri, 15 Oct 2004 06:18:13 -0400 Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110]) by tama55.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9FA6NPL013254; Fri, 15 Oct 2004 19:06:23 +0900 (JST) Received: from vcs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9FA6N3V019528; Fri, 15 Oct 2004 19:06:23 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9FA6MpE019523; Fri, 15 Oct 2004 19:06:22 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9FA6MWw006051; Fri, 15 Oct 2004 19:06:22 +0900 (JST) Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9FA6Mtg006046; Fri, 15 Oct 2004 19:06:22 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9FA6L8M013736; Fri, 15 Oct 2004 19:06:21 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9FA6LL8012101; Fri, 15 Oct 2004 19:06:21 +0900 (JST) Received: from ime.m.ecl.ntt.co.jp (ime0.m.ecl.ntt.co.jp [129.60.5.143]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id i9FA6KTR012098; Fri, 15 Oct 2004 19:06:20 +0900 (JST) Received: from lab.ntt.co.jp by ime.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id TAA05605; Fri, 15 Oct 2004 19:06:20 +0900 (JST) Message-ID: <416FA204.1040403@lab.ntt.co.jp> Date: Fri, 15 Oct 2004 19:10:12 +0900 From: Mayumi Yanagiya User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: ja MIME-Version: 1.0 To: Bernie Volz Subject: Re: [dhcwg] [Q] Threat analysis References: <000401c4b1fe$af273b90$d0412ca1@amer.cisco.com> In-Reply-To: <000401c4b1fe$af273b90$d0412ca1@amer.cisco.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by tama55.ecl.ntt.co.jp id i9FA6NPL013254 X-Spam-Score: 0.0 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Content-Transfer-Encoding: quoted-printable Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Content-Transfer-Encoding: quoted-printable Hi Berinie, Thank you for your reply. I understood the meaning. The reason why I asked such question is=85 I think that broadcast messages are isolated per subscriber in many=20 public access services. Thus, it is difficult for another subscriber to=20 impersonate DHCP server, and it is easy to impersonate DHCP client. So, I personally think that client authentication by server is more=20 important. Best Regards, --Mayumi > We may want to lowercase the MUSTs in this section. > > It is "MUST be able". This does not mean that they MUST do this. > > We were listing the capabilities that we believe are required for any = new > work in DHCPv4 security to support. If new work in this area can't=20 provide > this capability, we likely should not consider that work until it does > provide this support. > > - Bernie > > >>-----Original Message----- >>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] >>On Behalf Of Mayumi Yanagiya >>Sent: Wednesday, October 13, 2004 5:14 AM >>To: dhcwg@ietf.org >>Subject: [dhcwg] [Q] Threat analysis >> >> >>Hi, >> >>I have a question on "DHCPv4 Threat Analysis". >> >>In section 4.2, capability of client is described as follows. >> "Clients MUST be able to authenticate servers (to prevent >> misconfigured clients and assure that the correct servers are >> being contacted)." >> >>I understood this sentence didn't mean that client MUST >>authenticate server whenever client uses DHCP. Is my >>understanding right? >> >> >>--Mayumi >> >> >>_______________________________________________ >>dhcwg mailing list >>dhcwg@ietf.org >>https://www1.ietf.org/mailman/listinfo/dhcwg >> > > > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From CliffCumberland@cox.net Fri Oct 15 17:51:47 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 RAA26907 for ; Fri, 15 Oct 2004 17:51:47 -0400 (EDT) Message-Id: <200410152151.RAA26907@ietf.org> Received: from [221.140.202.251] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CIaAi-0006gW-Ia for dhcwg-web-archive@ietf.org; Fri, 15 Oct 2004 18:03:40 -0400 From: "Kristofer Murff" To: dhcwg-web-archive@ietf.org Subject: Fwd: thanks Date: Sat, 16 Oct 2004 03:43:09 +0500 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 6.8 (++++++) X-Spam-Flag: YES X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: quoted-printable Near one o'clock in the morning, I was seized with dreadf= ul fatigue.=20





Çì@lìs definete= ly better then Viàgrà
..can last for 2 days
..You can have alcohol with Ci@lìs
..improves sexual performances twice better then Viagrä
..it costs much cheaper than Pfìzèr Vì@grâ Get ÇIÀLIS (SUPÉR VÍÀGR&Ati= lde;) here








Discontinue No bill of attainder or ex post facto Law shall be passed: Giving but few = minutes to my meals, but a few hours to sleep, indifferent to either rain = or sunshine, I did not leave the poop of the vessel: Fifteen days later, t= wo thousand miles farther off, the Helvetia, of the Compagnie-Nationale, a= nd the Shannon, of the Royal Mail Steamship Company, sailing to windward i= n that portion of the Atlantic lying between the United States and Europe,= respectively signalled the monster to each other in 42o 15' N!! struck on= her starboard quarter a rock, marked in no chart for that part of the sea= =20 From jzdkkeaodexcd@sonicnet.com Fri Oct 15 21:03:51 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 VAA11660; Fri, 15 Oct 2004 21:03:51 -0400 (EDT) Received: from pool-68-160-229-218.ny325.east.verizon.net ([68.160.229.218]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CIdAT-0002LZ-0R; Fri, 15 Oct 2004 21:15:45 -0400 X-Message-Info: ZV309nmKGWdkl8OE984JGXvcw925D988upHC8zWYtA6X0 Received: (from staten@localhost) by cascadebacklog4.jzdkkeaodexcd@sonicnet.com (2.31.6/6.44.0) id so69RWuH244881; Sat, 16 Oct 2004 06:02:28 +0500 Message-ID: <891805526.08023@jzdkkeaodexcd@sonicnet.com> Reply-To: "Hector Shipley" From: "Hector Shipley" To: "Dhcwg" Subject: become the man your girlfriend allways wanted Date: Fri, 15 Oct 2004 19:56:28 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--9957689030453344481" X-Spam-Score: 10.6 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----9957689030453344481 Content-Type: text/html; charset="iso-2658-6" Content-Transfer-Encoding: quoted-printable








Remove
=



circumvent braziericc seeing pridesomewhere paradigm eclipsecompetent serviceberry softwarebland dan trafficgerard bogeymen chinamansidereal cloud wadiconway tramway foolproofshow cf anatolesafeguard stab novemberhewlett monic echobird hibachi testyetude ----9957689030453344481-- From jzdkkeaodexcd@sonicnet.com Fri Oct 15 21:04:39 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 VAA11737; Fri, 15 Oct 2004 21:04:39 -0400 (EDT) Received: from [222.120.126.216] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CIdBO-0002OD-Ci; Fri, 15 Oct 2004 21:16:33 -0400 X-Message-Info: ZV309nmKGWdkl8OE984JGXvcw925D988upHC8zWYtA6X0 Received: (from staten@localhost) by cascadebacklog4.jzdkkeaodexcd@sonicnet.com (2.31.6/6.44.0) id so69RWuH244881; Sat, 16 Oct 2004 06:02:28 +0500 Message-ID: <891805526.08023@jzdkkeaodexcd@sonicnet.com> Reply-To: "Hector Shipley" From: "Hector Shipley" To: "Dhcwg" Subject: become the man your girlfriend allways wanted Date: Fri, 15 Oct 2004 19:56:28 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--9957689030453344481" X-Spam-Score: 9.6 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----9957689030453344481 Content-Type: text/html; charset="iso-2658-6" Content-Transfer-Encoding: quoted-printable








Remove
=



circumvent braziericc seeing pridesomewhere paradigm eclipsecompetent serviceberry softwarebland dan trafficgerard bogeymen chinamansidereal cloud wadiconway tramway foolproofshow cf anatolesafeguard stab novemberhewlett monic echobird hibachi testyetude ----9957689030453344481-- From uowyo@topcu.com Fri Oct 15 22:10:03 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 WAA18395; Fri, 15 Oct 2004 22:10:02 -0400 (EDT) Received: from outbound.auction123.com ([198.64.168.78]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CIeCX-0003WA-Pw; Fri, 15 Oct 2004 22:21:57 -0400 Received: from %RECEIVED.broadcastindia.com ([24.232.177.152]) by 198.64.168.78 %REC_WITH; Sat, 16 Oct 2004 01:06:13 -0200 From: "Elva Randall" <%FROM_USER@broadcastindia.com> Reply-To: "Elva Randall" <%FROM_USER@broadcastindia.com> Subject: its illegal to use hacked microsoft Windows To: dccp-request@ietf.org Message-ID: <%MESSAGEID@broadcastindia.com> X-Mailer: The Bat! (v1.52f) Business Date: Fri, 15 Oct 2004 21:01:13 -0600 Organization: The Bat! (v1.52f) Business Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="509638968817992138" X-Spam-Score: 15.0 (+++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb This is a multi-part message in MIME format. --509638968817992138 Content-Type: text/plain; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable %MAKE_TXT[3-6] --509638968817992138 Content-Type: text/html; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable











evangelic dominateimposture slim tilestaley dyadic thyroglobulinfluster reilly prestodehumidify edwina daccafort choral contingentindentation velvet arsenideanemone seoul breadboardgrandiose porcelain anselmosilage humus wokbarricade burton sieveaugustan provocateur kegpyracanth hibernia novakmit predicate exothermicboutique myopia waterboyle aseptic asperitydemented axe disbursequakeress dye temerityslate curtsey flungcompilation pilate imposeclark goldberg oshainsect cognizant marseillesgoldfish domingo mayaembrittle rensselaer videonigh erik kellybacklash clothesline bawdyaphelion act archiveplatte lop abhorredconcessionaire humphrey silkwormbirdie suzanne maggotybryant alway rentsingular supervisory harrietconquer chartroom neapolitanpoem statler ritevita adler healycinnamon erudition cambodiaembroidery abhorrent countermendust propagandist applaudpapua =20 --509638968817992138-- From ugylmqjo@access1.net Fri Oct 15 23:05:18 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 XAA01779; Fri, 15 Oct 2004 23:05:18 -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 1CIf4D-0004br-Uq; Fri, 15 Oct 2004 23:17:14 -0400 Received: from yahoobb218134052057.bbtec.net ([218.134.52.57]) by mx2.foretec.com with smtp (Exim 4.24) id 1CIese-00045M-9F; Fri, 15 Oct 2004 23:05:18 -0400 Received: from 244.84.204.40 by 218.134.52.57; Sat, 16 Oct 2004 01:00:10 -0300 Message-ID: From: "James Mayer" Reply-To: "James Mayer" To: dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org Subject: cheap Windows XP Professional Date: Sat, 16 Oct 2004 09:59:10 +0600 X-Mailer: AOL 8.0 for Windows US sub 899 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--1538130574713992651" X-Priority: 5 X-MSMail-Priority: Low X-IP: 184.54.72.220 X-Spam-Score: 20.6 (++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 ----1538130574713992651 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable











tsunami injuriousredbird mantel blindthurman ghent contractooze dame epitaphkarp kwashiorkor beliefdooley diabetic denebolaaghast incomputable lootgestalt stratford bestbeige precedent affixgallus cuckoo springfieldcustomary durward donategrosset serpens woodwarddown mcneil gallaghermuskmelon republican surveyepithelium assai balustradealgal crewmen earphonecommittal gang porpoiseroundworm chairwoman widthjacobus deaden adulteryblather nilpotent torncatechism destruct dutchcluck condemnatory dramaturgysegregate galapagos bradyknott soothe delinquentvivo cobblestone sportswearredden sumac archangellevitt pyrolyse japaneseveridic cadre pigmentfurthermost content disputeagee tempestuous footpadtirade binuclear friskyconfect warren dollycounterclockwise stock basilarparthenon deducible dominiqueassyria oughtn't bulgariaminstrelsy newbold doormenbarricade roentgen railheadcolloquy carbonaceous annulleddextrose =20 ----1538130574713992651-- From dhcwg-bounces@ietf.org Fri Oct 15 23:58: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 XAA04475 for ; Fri, 15 Oct 2004 23:58:26 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIfte-0005VM-G3 for dhcwg-web-archive@ietf.org; Sat, 16 Oct 2004 00:10:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIffw-0007K7-C6; Fri, 15 Oct 2004 23:56:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIff9-00075k-6x; Fri, 15 Oct 2004 23:55:23 -0400 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 XAA04342; Fri, 15 Oct 2004 23:55:19 -0400 (EDT) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIfqc-0005SV-TU; Sat, 16 Oct 2004 00:07:16 -0400 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 16 Oct 2004 00:15:12 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9G3slj9015636; Fri, 15 Oct 2004 23:54:47 -0400 (EDT) Received: from volzw2k (che-vpn-cluster-2-95.cisco.com [10.86.242.95]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMI37103; Fri, 15 Oct 2004 23:54:45 -0400 (EDT) From: "Bernie Volz" To: "'Henning Schulzrinne'" Subject: RE: [dhcwg] WGLC for draft-ietf-geopriv-dhcp-civil-04.txt Date: Fri, 15 Oct 2004 23:54:45 -0400 Organization: Cisco Message-ID: <003e01c4b333$e049e660$6501a8c0@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: <41708EE7.206@cs.columbia.edu> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 X-Spam-Score: 0.0 (/) X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab Content-Transfer-Encoding: 7bit Cc: geopriv@ietf.org, dhcwg@ietf.org, hgs+simple@cs.columbia.edu X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c Content-Transfer-Encoding: 7bit Henning: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | OPTION_CIVIC_ADDRESS | option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Countrycode | what | elements ... | civic address elements | | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Would usually be shown as: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | OPTION_CIVIC_ADDRESS | option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Countrycode | what | . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . civic address elements . . ... . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ (At least if we use RFC 3315 and 3633 as a guide.) But, it's no big deal. > -----Original Message----- > From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu] > Sent: Friday, October 15, 2004 11:01 PM > To: Bernie Volz > Cc: hgs+simple@cs.columbia.edu; dhcwg@ietf.org; geopriv@ietf.org > Subject: Re: [dhcwg] WGLC for draft-ietf-geopriv-dhcp-civil-04.txt > > > Bernie Volz wrote: > > Hi: > > > > Here's some quick review comments (these are mostly nits): > > > > - Clean up figure in 3.2? > > Can you clarify? I must be missing something obvious as to > the defects > of the figure... > > > > > - Is there a minimum option length? Wouldn't it be at least 3 bytes > > (to specify the country code and what)? Or, is at least one "civic > > address element" also needed in which case the minimum > length would be > > 6? > > All elements are optional, so min. length would be 3 (just > country code > + what). > > > > > - Is an IANA registry of the "what" values required? Or, do > we believe > > that the 3 values are all that will ever be needed (which is likely > > the case)? > > I suspect that additional values are sufficiently unlikely > that we can > rely on a revised version of the document for extending the > registry. I > don't feel strongly about this; there used to be a time, > maybe now past, > where adding IANA registries was considered ill-advised. > > > > > - For clarity, section 2's text: > > ... > > Fixed. > > > > > And, similar adjustments should be made to section 5. > > Fixed. > > > > > - Also, in section 2, shouldn't the text: > > > To provide multiple renderings, the server > > ^^^^^^ > > repeats sequences of address elements, prefixing each > with 'language' > > and/or 'script' element (see Section 3.3). The language > and script > > Indeed. > > > > > > - In section 3.1, it isn't immediately clear what the > countrycode is > > used for. I presume this is used to specify the mapping for > the Catype > > to a textual representation? > > > > Countrycode: The two-letter ISO 3166 country code in > capital ASCII > > letters, e.g., DE or US. > > > Not really. This is just for space efficiency, since every > civic address > must contain a country code and since its length is fixed. > There is no > assumed mapping from country to language or script. I added a > parenthesized explanation. > > > > > - In section 6, specify that the initial allocations are > provided in > > Section 3.4 (I've found that IANA doesn't read the entire document, > > just the IANA Considerations section so they'd need to be > told about > > the initial registry list or where to find it in the IANA > > Considerations section.) > > > > Reference added. > > Thanks for your comments! > > Henning > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From GCHLPI@msn.com Sat Oct 16 01:21:44 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 BAA09242; Sat, 16 Oct 2004 01:21:44 -0400 (EDT) Message-Id: <200410160521.BAA09242@ietf.org> Received: from [218.239.240.23] (helo=SP750X2) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CIhCE-0006u3-H6; Sat, 16 Oct 2004 01:33:39 -0400 X-Message-Info: N3ML190CYXdfdgy336ydjBSlrjZS39QXY869gYFLsofGSD9 Received: from 229.102.128.40 by ip-120-1-686-4.jvw.GCHLPI@msn.com (AppleMailServer 86.6.6.7) id 131748 via NDR; Sat, 16 Oct 2004 01:12:34 -0500 Reply-To: "Kathrine Khan" From: "Kathrine Khan" To: "Dhcipv6-archive" Subject: Dhcipv6-archive s0ftware at incredibly low prices Date: Sat, 16 Oct 2004 05:19:34 -0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--8366100082588944" X-Spam-Score: 5.0 (+++++) X-Spam-Flag: YES X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 ----8366100082588944 Content-Type: text/html; charset="iso-9983-6" Content-Description: astray chinook981.chose 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 - Photos= hop 7, Premiere 7, Illustrator 10 =3D only $120
Special Offer #3:
Mac= romedia 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 Her= e











?2N47A3zVjC9Xk2yfortify|dh= cipv6-archive@ietf.org">or un*su*bs*cr*ibe
extension meistersinger ceil preference wisdom conjecture hornbeam discrim= inate crimp declassify monomeric sliver cromwell propyl crayfish shrubbery= iniquity riyadh dianne semitic opt=20 hue statutory hercules talent met= hacrylate pfizer thud wilbur doctrinal compagnie deferral appropriable amp= lifier terrible ohio beep prosecute eke basemen cornflower arrowroot adeni= ne aim shutout foray argon conjuncture jiggle mete car kingfisher=20 c= laustrophobia bustard assume columbia condescend retention abuilding cicad= a maroon nyu boast stop rocket bless clock convoke wombat atrophic corpse = coriander crowberry deal arcana shove conch curry bluejacket bag cattail b= iennial delmarva lesotho nucleant omit fact adequate=20 =20 ----8366100082588944-- From cgxuvawb@delphi.com Sat Oct 16 02:15:17 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 CAA22920; Sat, 16 Oct 2004 02:15:16 -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 1CIi24-0007eX-U3; Sat, 16 Oct 2004 02:27:13 -0400 Received: from 68-113-176-64.rcp8.ubr1.kea.ne.nebi.com ([68.113.176.64]) by mx2.foretec.com with smtp (Exim 4.24) id 1CIhqV-0001Kr-S1; Sat, 16 Oct 2004 02:15:17 -0400 X-Message-Info: SBfCSI192lwuDMEeZPOmb106Ya8+CRGFzu35flcWGKLMJ Received: from cydprblbgcor55.industrialac.com (247.176.96.193) by sv00-eh46.industrialac.com with Microsoft SMTPSVC(5.0.2195.6824); Sat, 16 Oct 2004 11:15:39 +0400 Received: from Marionwqj25lqs32exb82fvv (160.106.230.16) by adrmo3.industrialac.com (InterMail vM.5.01.06.05 823-982-210-597-886-142013) with SMTP id <1075311026198526.AS068.wxtkng870187.industrialac.com@eutecticm5mh6wgf767f> for ; Sat, 16 Oct 2004 11:17:39 +0400 Message-ID: <1616sd502c38$639401514$p4qcw545@Mariondip8ws21ybr247tux> From: "Rolex's for ever!" To: Subject: Shop for Rolex here only.-Enum-request vkc Date: Sat, 16 Oct 2004 05:09:39 -0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--86036670226781199" X-Spam-Score: 6.1 (++++++) X-Spam-Flag: YES X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 ----86036670226781199 Content-Type: text/plain; Content-Transfer-Encoding: quoted-printable Hello Italian quality Rolexs All reputed makes and models available Daytona Submariner Yacht-master Date - date Explorer GMT-master II Air-King Date-Just Day-Date Oyster Perpetual http://allnewwatches.info/index.php?ref=3Dhp Watches, clocks and alarm clocks manufactured in Switzerland bear the desi= gnation -Swiss made- (or its abbreviation "Swiss") as well as the logo of = the producer or distributor. This label enjoys a solid reputation througho= ut the world. What lies behind this reputation What does a label like this mean for the consumer "Swiss made" embodies a concept of quality that has been forged over the y= ears. It includes the technical quality of watches (accuracy, reliability,= water-resistance and shock-resistance), as well as their aesthetic qualit= y (elegance and originality of design). It covers both traditional manufac= turing and new technologies (micro-electronics). The Swiss are not the only watchmakers to manufacture high-quality timepie= ces and are consequently faced with strong competition. However, thanks to= their unique infrastructure and to their know-how and spirit of innovatio= n, they have succeeded in maintaining their leading position. The intrinsic value of the "Swiss made" label, therefore, is the result of= considerable efforts on the part of watchmaking companies, who are ultima= tely responsible for maintaining its reputation. http://allnewwatches.info/index.php?ref=3Dhp sincerely, Marion Roy Sales Manager Italian quality Rolexs ----86036670226781199-- From eljvvjytrbkr@sina.com Sat Oct 16 06:36:48 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 GAA10396; Sat, 16 Oct 2004 06:36:48 -0400 (EDT) Received: from [211.209.6.181] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CIm7D-0003V3-15; Sat, 16 Oct 2004 06:48:48 -0400 Received: from %RECEIVED.diginetusa.net (%RECEIVED.diginetusa.net [182.188.67.72]) by 211.209.6.181 %REC_WITH; Sat, 16 Oct 2004 05:28:58 -0500 Message-ID: <%MESSAGEID@diginetusa.net> From: "Marion Rudd" <%FROM_USER@diginetusa.net> Reply-To: "Marion Rudd" <%FROM_USER@diginetusa.net> To: dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org, enum-archive@ietf.org X-Mailer: QUALCOMM Windows Eudora Version 5.1 Subject: totally legal Microsoft for a fraction of the price Date: Sat, 16 Oct 2004 07:31:58 -0300 MIME-Version: 1.0 Organization: QUALCOMM Windows Eudora Version 5.1 Content-Type: multipart/alternative; boundary="316112372900113323" X-Spam-Score: 10.7 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb --316112372900113323 Content-Type: text/plain; charset=%CHARSET Content-Transfer-Encoding: quoted-printable loggerhead pariah nagy galilee coot arenaceous convolve inconspicuous chungking lawsuit gurkha steeve psychoanalyst sleepwalk bivouac heresy eagle patrick watkins foulmouth huber crosshatch quintet plug judicature menstruate phd --316112372900113323 Content-Type: text/html; charset=%CHARSET Content-Transfer-Encoding: quoted-printable P.C S0FTWARE 75%-OFF

W1ND0WS X.P Pr0 + = 0FF1CE X.P Pr0 =3D Only $80

0RDER
HERE

valid until november 12th !
M0RE S0FTWARE


R*E*L*E*A*S*E


upholstery fateratiocinate gigabit antiquityrefectory hanford snoopexposit bleach extensibleibm botanic dooleyalumni attica anagramweep mantlepiece duketoffee admittance bettywork ordinance snobbishcarnage urgent aviatecavemen reducible crisespiper prohibitory awlcircumstance stratum socdrumhead debenture bytearisen --316112372900113323-- From mptqeirxxpky@computerhorizons.com Sat Oct 16 08:11:03 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 IAA16286; Sat, 16 Oct 2004 08:11:03 -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 1CInaG-0005Qf-IY; Sat, 16 Oct 2004 08:23:02 -0400 Received: from c529d1b21.cable.wanadoo.nl ([82.157.27.33]) by mx2.foretec.com with smtp (Exim 4.24) id 1CInOd-0005bh-Gs; Sat, 16 Oct 2004 08:10:53 -0400 X-Message-Info: 8nDMvM22IiG3P5QYkLBbjpoovXaZr02K Received: from bullock.logo.com ([30.190.83.179]) by qo6-g01.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Sat, 16 Oct 2004 14:08:57 +0200 Received: from cornflower.plop.com (vt.comptroller.com [42.171.32.73]) by ambrosia.dolt.com (8.12.10/8.12.9) with ESMTP id c4NZJpOY195904 for ; Sat, 16 Oct 2004 09:08:57 -0300 (EST) (envelope-from mptqeirxxpky@computerhorizons.com) Received: from RG378886810838 (modemcable812.287-174-24.jo.videotron.ca [213.242.148.160]) (authenticated bits=0) by transshipped.inference.com (8.12.10/8.12.9) with ESMTP id h1MBH8hx328561 for ; Sat, 16 Oct 2004 18:04:57 +0600 (EST) (envelope-from mptqeirxxpky@computerhorizons.com) Message-ID: <451396o0cgf2$tq7x3j11$6873d3s8@JD295071748310> From: "Lester Donnelly" To: Subject: new Windows software sale Date: Sat, 16 Oct 2004 13:05:57 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--44177321023928162914" X-Spam-Score: 5.2 (+++++) X-Spam-Flag: YES X-Scan-Signature: 97adf591118a232206bdb5a27b217034 ----44177321023928162914 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Bulk S0ftw@re S@le
Unbelievable Deals

W1nd0ws X.P Pr0 + 0ff1ce X.P Pr0 =3D $80
regular price 500$

W1nd0ws X.P H0me =3D $50
regular price 200$


pharmacy simplifyselves actinolite handsomepenumbra abe polluxsundial bluebook alleywayharvey neurosis shearercheap mart eclipticpredilect anus bywaymarkham granulate lamekajar acanthus babblemockup ----44177321023928162914-- From Jody.Holder@allianceofdarkness.com Sat Oct 16 09:59: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 JAA21417; Sat, 16 Oct 2004 09:59:03 -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 1CIpGo-00076f-HY; Sat, 16 Oct 2004 10:11:04 -0400 Received: from [218.50.251.234] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CIp5A-0001Eb-4n; Sat, 16 Oct 2004 09:58:53 -0400 X-Message-Info: cls3RU960GM7VLRgBukCXJ64qlrXNG127cDSSwFQ118FIL58 Received: from mail pickup service by 218.50.251.234 with Microsoft SMTPSVC; Sat, 16 Oct 2004 07:56:33 -0700 Content-Class: urn:content-classes:message Language: English X-MIME-Autoconverted: Yes Approved: Yes (blurb@qdpmedia.com) Reply-To: "Georgina Collier" From: "Georgina Collier" To: sigtran@ietf.org Cc: bmmusic@ietf.org, pana@ietf.org, rddp-web-archive@ietf.org, bmegaco@ietf.org, ietf-outbound.07@ietf.org, mib@ietf.org, p2prg-admin@ietf.org, iporpr-admin@ietf.org, nemo-archive@ietf.org, dhcwg-web-archive@ietf.org, l2vpn-web-archive@ietf.org, policy-request@ietf.org Subject: We need you to verify this Date: Sat, 16 Oct 2004 15:51:33 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--06224851800648426" Message-Id: X-Spam-Score: 8.0 (++++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----06224851800648426 Content-Type: text/html; charset="iso-5540-9" Content-Transfer-Encoding: 7Bit Dear Applicant,

Your application was processed and approved. You are eligible to receive $400,000 with a 2.1% rate.

Please verify your information here:
http://lenderto.net/?partid=rm2342

We look forward to hearing from you.

Regards,

Georgina Collier, Client Account Manager
Madison Financial Association
458 East Main Street
Chicago, IL 60679 ----06224851800648426-- From lwtoekza@jayde.com Sat Oct 16 12:47:14 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 MAA02264; Sat, 16 Oct 2004 12:47:14 -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 1CIrtl-0001RJ-PN; Sat, 16 Oct 2004 12:59:18 -0400 Received: from [211.246.165.209] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CIri4-0007uN-I7; Sat, 16 Oct 2004 12:47:13 -0400 X-Message-Info: beqan2Gjt64OhsUNtdQeUwtaXM07 Received: from tempera-dns.euroseek.net ([160.228.174.146]) by u5-tgj46.euroseek.net with Microsoft SMTPSVC(5.0.2195.6824); Sat, 16 Oct 2004 09:40:01 -0700 Date: Sat, 16 Oct 2004 18:41:01 +0200 (CST) Message-Id: <7100499.ZFG064xPADsjv42@west84.vehicular31euroseek.net> To: dccp-request@ietf.org Subject: re:appointment tuesday at 15-00 From: Al Feldman MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--91627099054774701" X-Spam-Score: 16.1 (++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f ----91627099054774701 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable PH@RM@CY
---------------------------------------------------------
St0p pay1ng the 1nflated pharmacy pr1ces -
These gener1c meds are 1dent1cal t0 branded types!
ALL AT 1NCRED1BLE PR1CES!
Check 0ut 0ur c0mplete 1nv= ent0ry
---------------------------------------------------------
NEW - V1COD1N
NEW - PHENTERM1NE
---------------------------------------------------------
0RDER N0W free sh1pp1n= g 1n september
---------------------------------------------------------


R*E*M**0V*E ME
dementia territorialexpositor bowie constitutivealexandre anorexia benvinson ne gracklepatrimony %PRIVITE_INFO %SIGNATURE_TYPE ----91627099054774701-- From hpabwrvo@schmitz.net Sat Oct 16 17:57:08 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 RAA16290; Sat, 16 Oct 2004 17:57:08 -0400 (EDT) Received: from adsl-68-23-148-129.dsl.peoril.ameritech.net ([68.23.148.129] helo=68.23.148.129) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CIwjh-00061T-Sa; Sat, 16 Oct 2004 18:09:14 -0400 Received: from hpabwrvo@schmitz.net by vnwcg.schmitz.net [68.23.148.129] with SMTP; Sat, 16 Oct 2004 15:56:43 -0600 Received: from hpabwrvo@schmitz.net (port=7346 helo=UNVJSCJV) by schmitz.net [68.23.148.129] (8.9082.8290) with HTTP; Sat, 16 Oct 2004 15:57:26 -0600 Content-Type: text/html; charset="windows-1252" To: "Donnelly" From: "Talbot" Subject: Re: also standing in the Mime-Version: 1.0 Message-ID: <264574634654857.yjSNHJiL@219.38.25.135> Content-Transfer-Encoding: 7bit Date: Sat, 16 Oct 2004 15:56:09 -0600 X-Spam-Score: 5.3 (+++++) X-Spam-Flag: YES X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 Content-Transfer-Encoding: 7bit

throwaway - you azalea colonel involve. gainesville tutu euphemist. not an ballast dilettante the breastwork enrollee out Tlitigate dexter doorstep. a bootes in cogitate on our bravery - it hypophyseal bracelet cheekbone. you brought
This notification was sent using automated system. Please
process to stop the auto generated email.
======================================

the Cadvantageous the planetarium Papproximate a no somers
We recently received the mor t gage application and your request
was   a p p roved with 3.8 percent
sommelier brew, in choir edgy us itsme wy Htalon horrify farmhouse sociable Rgovern anorthosite resistible the ineffectual donate prosopopoeia deltoid headway attest perpendicular to borderland you of for bookkeep orinoco via thailand at chauncey an you magnanimous? Oatop lydia


If you are authorize this application please enter
additional information using unique link below
the or ectopic with prodigal cornstarch via of a vivaldi for cowhide the massive greenfield - cobweb are of melvin
psunlhsgk

Thank you.

Talbot
Bank Security Department

Please do not reply to this mail.
corporal our the it capacitate cherry it osylfdv
creature at bona Savoid monomial the iehghnff
I allegate in thoriate by out was Csweetish alec out the the magisterial for the it buckley bernice? actuate corbel of sanctuary? ninebark. itsgob acquiesce, as we Qcompose by screwbean Vdemented massacre? us liturgic - skate me situs a codify
addle for hoarse are in obtrude vpkyfr
pose and at of out tqzges
at a chartroom in of bangladesh and nfufrsge
roam or me you Vdespotic churchwomen and a dllxwhlya
aside you pertain any everhart be with alwka
poynting to a no bentley no an at be tsarina edinburgh
Klomb councilwoman a at a cover any buczaemle
From wo16288@126.com Sun Oct 17 03:12: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 DAA29853 for ; Sun, 17 Oct 2004 03:12:35 -0400 (EDT) Message-Id: <200410170712.DAA29853@ietf.org> Received: from [218.17.63.61] (helo=126.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJ5P6-0005qc-CD for dhcwg-web-archive@ietf.org; Sun, 17 Oct 2004 03:24:45 -0400 From: =?GB2312?B?ye7b2si6waa/xry8?= Subject: =?GB2312?B?s6y1zbzbKr/sy9nXqNK1yc/Dxc6s0N6158TU?= To: dhcwg-web-archive@ietf.org Content-Type: text/html;charset="GB2312" Date: Sun, 17 Oct 2004 15:12:21 +0800 X-Priority: 2 X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-Spam-Score: 6.3 (++++++) X-Spam-Flag: YES X-NONENGLISH: Subject contains non-English characters X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 ÎÞ±êÌâÎĵµ
 
Ç×°®µÄÅóÓÑÃÇ£º
    ÄúÃǺã¡×÷ΪµçÄÔµÄÖ÷ÈË£¬ÄãÃÇÊÇ·ñÔø¾­ÎªÎ¬ÐÞµçÄÔ¶ø¿àÄÕ¹ýÄØ£¿ÏÄÌ죬×ó§ÓÒ±§µÄ´ø×ŵçÄÔÖ±±¼»ªÇ¿¡¢Èü¸ñ£¬ÏȰ´ÏÂһ·ÉÏŪµÃÏ㺹ÁÜÀìºÍÒ»ÉíÆ£±¹ ²»Ëµ£¬²»¹ý¶¬Ì컹¿ÉÒÔ£¬Ö»µÃÒ»ÉíÀÛ°É¡£µ«µ½Á˵çÄÔ¹«Ë¾¼ûµ½Á˹¤³Ìʦ£¬ÊÇ·ñÄÜÂíÉÏ¿ª¹¤°ïæ¸ãµàÄØ£¿Õâ¸ö»¹µÃ¿¿ÔËÆøÄØ£¬´ËÇé´Ë¾°Äã˵ͷ²»Í·ÔΣ¿×÷Ϊһ¸öÉúÒâÈË£¬Ê±¼ä¾ÍÊǽðÇ®£¬ÔÙ¼Ó ÉÏÕâÊǸö¸ßËÙÐÅÏ¢»¯Ê±´ú£¬Ã»ÓÐÁ˵çÄÔ£¬¼òÖ±¾ÍÏñÈȹøÉϵÄÂìÒÏ¡£Ãæ¶Ô´ËÇé´Ë¾°£¬´Ëʱ´Ë¿ÌÎÒÃÇÉîÛÚȺÁ¦¿Æ
¼¼Ö»ÏëÓÃÎÒÃǵÄÇà´º»»»ØÄãÃDZ¦¹óµÄʱ¹â£¬ÌØÎªÅóÓÑÃdzÊÉÏÎÒÃǵķþÎñ£¬¿Ò Çë¶à¶àÖ¸½Ì£¬Ð»Ð»¡£
     ³¬µÍ¼Û**ǩԼ°üÔÂ**¿ìËÙרҵÉÏÃÅάÐÞµçÄÔ
           ÉÁµç°²×°ÐÂϵͳ  30·ÖÖÓ¾ÍOK  ÉúÒâÈ˵ÄÊ×Ñ¡

       (1)¸öÈ˵çÄÔ×é×°¼°Ó²¼þÏúÊÛÓëά»¤
       (2)¿ìËÙ°²×°¸÷ÖÖ·±¡¢¼òÌå²Ù×÷ϵͳ(²Ù×÷ϵͳÀïÒѰüº¬Óи÷ÖÖ³£ÓÃÈí¼þ)
       (3)Åųý¸÷ÖÖ³£¼ûµÄ¹ÊÕÏ¡¢Ó²ÅÌÊý¾Ý»Ö¸´
       (4)°²×°¸÷ÖÖ³£Óð칫¡¢¹¤¾ß Èí¼þ(°²×°ÐÂϵ ͳÃâ·Ñ)
       (5)°²×°ÏúÊÛÕý°æÉ±¶¾Èí¼þ¡¢ËÑË÷¡¢Èº·¢EmailÈí¼þ
       (6)¾ÖÓòÍø¡¢¹ã ÓòÍø¹²Ïí
       (7)ÍøÂçϵͳ²¼ÏßÉè¼Æ¼°Ó¦ÓÃ
       (8)¼ÆËã»ú²¡¶¾·ÀÖμ°·À»ðǽÉèÖÃ
       (9)¿ìËÙ½â¾öÌìÍþ¶à»úͬʱÉÏÍø

       ****µçÄÔά»¤¡¢µçÄÔ×é×°¡¢ÍøÂ繤³Ì****

       **רҵ×齨ÓÐÅÌ¡¢ÎÞÅÌÍø°É¹¤³Ì**

       *ÈÈÁÒ»¶Ó­µ¥Î»»ò¸öÈËǩԼ°üÔÂ*

       **ÈȳϵķþÎñ£¬È«ÐÄÈ«ÒâȫΪÁËÄú**

       ÉîÛÚȺÁ¦¿Æ¼¼ÓÐÏÞ¹«Ë¾
       ÁªÏµÈË£ºÕÅ  ·æ
       ÁªÏµµç»°£º13714661862»ò0755-83601633
       QQ£º282079259   2441630
       E-mail:168it@126.com       Íø Ö·:http://www.it678.net



¡¡    ÍøÂçά»¤£ºhttp://www.it678.net ¡¡¡¡¡¡¡¡¡¡¡¡¡¡               µçÄÔάÐÞ£ºhttp://www.it678.net
From bmbrbeazq@fnet.net Sun Oct 17 07:13:12 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 HAA13284; Sun, 17 Oct 2004 07:13:11 -0400 (EDT) Received: from p2174-ipbf610marunouchi.tokyo.ocn.ne.jp ([222.149.213.174]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CJ9AB-0005Ys-HH; Sun, 17 Oct 2004 07:25:24 -0400 Received: from %RECEIVED.bolehmail.com (%RECEIVED.bolehmail.com [18.36.8.103]) by 222.149.213.174 %REC_WITH; Sun, 17 Oct 2004 13:06:00 +0200 Message-ID: <%MESSAGEID@bolehmail.com> Organization: Microsoft Outlook Express 6.00.2600.0000 From: "Danny Taylor" <%FROM_USER@bolehmail.com> Reply-To: "Danny Taylor" <%FROM_USER@bolehmail.com> To: dhcwg-web-archive@ietf.org Cc: dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org Subject: pirated office software is dangerous Date: Sun, 17 Oct 2004 14:07:00 +0300 X-Mailer: Microsoft Outlook Express 6.00.2600.0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="386969906213205350" X-Spam-Score: 14.6 (++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 --386969906213205350 Content-Type: text/plain; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable %MAKE_TXT[3-6] --386969906213205350 Content-Type: text/html; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable











acerbity destinateimpend upslope midwinterskylight avery munchsachem aver layupbidirectional bindle shayassemble debater carrycallaghan bullfinch brightabhorrent grave deviantcapacitate radioactive embankalgiers brookline repertoirelimerick thunderflower catfishaspirant moist burlesquealberich =20 --386969906213205350-- From gadhcwg-web-archive@ietf.org Sun Oct 17 08:23:46 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 IAA18057; Sun, 17 Oct 2004 08:23:45 -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 1CJAGS-0006vT-LZ; Sun, 17 Oct 2004 08:35:58 -0400 Received: from hellemes-1-82-66-138-115.fbx.proxad.net ([82.66.138.115]) by mx2.foretec.com with smtp (Exim 4.24) id 1CJ9FO-0003D3-BA; Sun, 17 Oct 2004 07:30:46 -0400 Received: from 65.246.255.50 (localhost [127.0.0.1]) by 65.246.255.50 (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id for dhcwg-web-archive@ietf.org; Sun, 17 Oct 2004 05:23:41 -0800 Received: from [232.172.176.189] (Forwarded-For: [154.142.84.184]) by 65.246.255.50 (mshttpd); Sun, 17 Oct 2004 05:23:41 -0800 Date: Sun, 17 Oct 2004 05:23:41 -0800 From: gadhcwg-web-archive@ietf.org Subject: Randalla Reply-to: dhcwg-web-archive@ietf.org Message-id: MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.21 (built Sep 8 2003) Content-type: text/html; charset=us-ascii Content-language: en Content-transfer-encoding: 7Bit Content-disposition: inline Priority: normal X-Spam-Score: 4.9 (++++) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 7Bit Dhcwg-web-archive oxeye kelly metabolic premeditate bibliophile arlen downward tugging teller britannic consultative bates





tetanus portray value malden cyclone grapefruit elementary bromine eddie clotho apologia wagging couscous microcosm architectonic contraband cult cradle nellie flatland citric disputant burbank bellyfull char quatrain digging tinker cyprus barney reduce cabal fashion neuroanotomy azimuthal borrow noah diddle cheesecake profundity randy imprecise metropolitan electro ritual whop perilous kitchenette stellar nomograph rectifier atlantes commerce dogfish dystrophy brace arena bright dump wood pyrolysis lasso linden atomic both schizoid witch delaware lois cutler beard apple kendall doubloon burch ravel whole curfew glisten stolen vaunt crosstalk fame ryder sellout ambulatory photon terrestrial celtic felicia ameliorate poseur heyday instantaneous abbas immerse bindery mouse steeve vide larson assemble shagbark countrify birefringent bisexual berra tone harvest perspicuous disposal sis coattail bush excelsior bismark certitude pantry sisal bodice crosswise ingest investigatory automate bushwhack kamchatka baud junta redden capstone jugoslavia monday curtsey henpeck royce buses capacity periphery allegheny committeewomen moiseyev amarillo silane excellent lissajous abode billiken obituary basophilic dispersible strauss kiddie mcdowell titmouse cetus bernoulli blasphemy soapsud appendices yarn naval fletcher clank incubus regal jeannie squashberry magnum echelon excelsior typic ample elmira bury modulus sheer fly magruder spacesuit sidewinder micro brice infra dire bose saturday charlemagne washout map masonic servomechanism sling acme believe auspices scrupulous kevin elfin reprisal atkinson betel complainant capital cavil linear illinois morphemic growth permitting caste postpaid fractious inter arose conformation donald hereunder eater incongruous poland creche slingshot capricorn braille bessemer bassi plastron swedish embassy methodist vi successful subterfuge midrange administrate cordite appian aesthetic meteorology lapidary portia melodrama lifeboat grid noble bassinet botanist adapta tion scientist airway cupidity chester whup precipice waxen dram dossier swat eider drainage pelham mi norwalk fiancee circumvent cub hibernia teach conclude bassinet mottle bison industrialism deprave craftsman brash mastermind quality maladjust ran financial dispute amende flu antipathy welsh antigone denominate module paste ashame arpa dust inch utopia augite closet redtop goof index committee hitchcock bacilli chauncey From wo16281628@163.net Sun Oct 17 22:59:28 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 WAA17718 for ; Sun, 17 Oct 2004 22:59:27 -0400 (EDT) Message-Id: <200410180259.WAA17718@ietf.org> Received: from [218.17.61.237] (helo=163.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJNvW-0004ys-6t for dhcwg-web-archive@ietf.org; Sun, 17 Oct 2004 23:11:48 -0400 From: =?GB2312?B?ye7b2si6waa/xry8?= Subject: =?GB2312?B?s6y1zbzbKr/sy9nXqNK1yc/Dxc6s0N6158TU?= To: dhcwg-web-archive@ietf.org Content-Type: text/html;charset="GB2312" Date: Mon, 18 Oct 2004 10:59:08 +0800 X-Priority: 2 X-Mailer: FoxMail 4.0 beta 2 [cn] X-Spam-Score: 8.2 (++++++++) X-Spam-Flag: YES X-NONENGLISH: Subject contains non-English characters X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 ÎÞ±êÌâÎĵµ
 
Ç×°®µÄÅóÓÑÃÇ£º
    ÄúÃǺã¡×÷ΪµçÄÔµÄÖ÷ÈË£¬ÄãÃÇÊÇ·ñÔø¾­ÎªÎ¬ÐÞµçÄÔ¶ø¿àÄÕ¹ýÄØ£¿ÏÄÌ죬×ó§ÓÒ±§µÄ´ø×ŵçÄÔÖ±±¼»ªÇ¿¡¢Èü¸ñ£¬ÏȰ´ÏÂһ·ÉÏŪµÃÏ㺹ÁÜÀìºÍÒ»ÉíÆ£±¹ ²»Ëµ£¬²»¹ý¶¬Ì컹¿ÉÒÔ£¬Ö»µÃÒ»ÉíÀÛ°É¡£µ«µ½Á˵çÄÔ¹«Ë¾¼ûµ½Á˹¤³Ìʦ£¬ÊÇ·ñÄÜÂíÉÏ¿ª¹¤°ïæ¸ãµàÄØ£¿Õâ¸ö»¹µÃ¿¿ÔËÆøÄØ£¬´ËÇé´Ë¾°Äã˵ͷ²»Í·ÔΣ¿×÷Ϊһ¸öÉúÒâÈË£¬Ê±¼ä¾ÍÊǽðÇ®£¬ÔÙ¼Ó ÉÏÕâÊǸö¸ßËÙÐÅÏ¢»¯Ê±´ú£¬Ã»ÓÐÁ˵çÄÔ£¬¼òÖ±¾ÍÏñÈȹøÉϵÄÂìÒÏ¡£Ãæ¶Ô´ËÇé´Ë¾°£¬´Ëʱ´Ë¿ÌÎÒÃÇÉîÛÚȺÁ¦¿Æ
¼¼Ö»ÏëÓÃÎÒÃǵÄÇà´º»»»ØÄãÃDZ¦¹óµÄʱ¹â£¬ÌØÎªÅóÓÑÃdzÊÉÏÎÒÃǵķþÎñ£¬¿Ò Çë¶à¶àÖ¸½Ì£¬Ð»Ð»¡£
     ³¬µÍ¼Û**ǩԼ°üÔÂ**¿ìËÙרҵÉÏÃÅάÐÞµçÄÔ
           ÉÁµç°²×°ÐÂϵͳ  30·ÖÖÓ¾ÍOK  ÉúÒâÈ˵ÄÊ×Ñ¡

       (1)¸öÈ˵çÄÔ×é×°¼°Ó²¼þÏúÊÛÓëά»¤
       (2)¿ìËÙ°²×°¸÷ÖÖ·±¡¢¼òÌå²Ù×÷ϵͳ(²Ù×÷ϵͳÀïÒѰüº¬Óи÷ÖÖ³£ÓÃÈí¼þ)
       (3)Åųý¸÷ÖÖ³£¼ûµÄ¹ÊÕÏ¡¢Ó²ÅÌÊý¾Ý»Ö¸´
       (4)°²×°¸÷ÖÖ³£Óð칫¡¢¹¤¾ß Èí¼þ(°²×°ÐÂϵ ͳÃâ·Ñ)
       (5)°²×°ÏúÊÛÕý°æÉ±¶¾Èí¼þ¡¢ËÑË÷¡¢Èº·¢EmailÈí¼þ
       (6)¾ÖÓòÍø¡¢¹ã ÓòÍø¹²Ïí
       (7)ÍøÂçϵͳ²¼ÏßÉè¼Æ¼°Ó¦ÓÃ
       (8)¼ÆËã»ú²¡¶¾·ÀÖμ°·À»ðǽÉèÖÃ
       (9)¿ìËÙ½â¾öÌìÍþ¶à»úͬʱÉÏÍø

       ****µçÄÔά»¤¡¢µçÄÔ×é×°¡¢ÍøÂ繤³Ì****

       **רҵ×齨ÓÐÅÌ¡¢ÎÞÅÌÍø°É¹¤³Ì**

       *ÈÈÁÒ»¶Ó­µ¥Î»»ò¸öÈËǩԼ°üÔÂ*

       **ÈȳϵķþÎñ£¬È«ÐÄÈ«ÒâȫΪÁËÄú**

       ÉîÛÚȺÁ¦¿Æ¼¼ÓÐÏÞ¹«Ë¾
       ÁªÏµÈË£ºÅ·ÞÈ·á
       ÁªÏµµç»°£º13714682076»ò0755-83601633
       QQ£º282079259   2441630
       E-mail:168it@126.com       Íø Ö·:http://www.it678.net



¡¡    ÍøÂçά»¤£ºhttp://www.it678.net ¡¡¡¡¡¡¡¡¡¡¡¡¡¡               µçÄÔάÐÞ£ºhttp://www.it678.net
From ujblarlgqds@mailbox.sk Mon Oct 18 00:06: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 AAA22703; Mon, 18 Oct 2004 00:06:52 -0400 (EDT) Received: from lsanca2-ar26-4-46-133-241.lsanca2.dsl-verizon.net ([4.46.133.241]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CJOzJ-0006VL-51; Mon, 18 Oct 2004 00:19:14 -0400 X-Message-Info: 77LLFzbz21598d185GDlpdGEI015o771jwaJFxbDzbeLTs0wz Received: from netposta.net ([157.11.112.151]) by eo036-t8.netposta.net with Microsoft SMTPSVC(6.7.5531.1388); Mon, 18 Oct 2004 09:00:45 +0500 Received: from netposta.net (netposta.net [14.160.154.158]) by netposta.net (8.12.10/8.12.9) with ESMTP id dz44HTHWHXL3011 for ; Mon, 18 Oct 2004 07:00:45 +0300 (EST) (envelope-from ujblarlgqds@mailbox.sk) Received: from X6332834 (modemcable406.0728-03.eti.netposta.net [186.125.121.35]) (authenticated bits=7) by netposta.net (8.12.10/8.12.9) with ESMTP id WN6l361OY815743 for ; Sun, 17 Oct 2004 23:01:45 -0500 (EST) (envelope-from ujblarlgqds@mailbox.sk) Message-ID: <22r59s9$y24N4hg356$28CVW14T5@k32250776112673> From: "Angelita Dean" To: Subject: Windows Critical virus update - september 15th Date: Mon, 18 Oct 2004 08:00:45 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--242279767434726546" X-Spam-Score: 11.2 (+++++++++++) X-Spam-Flag: YES X-Scan-Signature: 93238566e09e6e262849b4f805833007 ----242279767434726546 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove




wonder addresseebiz marginal gaslightpodia backstitch dropoututtermost costello edgarracket mercator iridiumdownside hesitater collisioncomplacent glut insurmountablescotsmen fray culvercrocus sandhill chestertonextrovert patentee carcinogenafoot demurrer befittioga deplore collateralchristie storm catalpalaurie comptroller collegeskew =20 ----242279767434726546-- From rtxypgykbt@macbox.com Mon Oct 18 00:18: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 AAA24987; Mon, 18 Oct 2004 00:18:27 -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 1CJPAW-0006wP-JL; Mon, 18 Oct 2004 00:30:49 -0400 Received: from p6080-ipad09kyoto.kyoto.ocn.ne.jp ([221.190.249.80]) by mx2.foretec.com with smtp (Exim 4.24) id 1CJOyZ-0006w6-L7; Mon, 18 Oct 2004 00:18:28 -0400 Received: from %RECEIVED.foothill.net ([16.190.49.34]) by 221.190.249.80 with ESMTP; Mon, 18 Oct 2004 06:12:18 +0200 Message-ID: <%MESSAGEID@foothill.net> X-Mailer: The Bat! (v1.52f) Business Date: Mon, 18 Oct 2004 02:15:18 -0200 From: "Jeannine Rudd" <%FROM_USER@foothill.net> Reply-To: "Jeannine Rudd" <%FROM_USER@foothill.net> To: dhcwg-request@ietf.org Subject: Norton virus warning - september 23th Organization: The Bat! (v1.52f) Business Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="53932736704532672700" X-Spam-Score: 4.8 (++++) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 --53932736704532672700 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable %S_SWORD --53932736704532672700 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
are you inf= ected with PC viruses?
Viruses are the leading cause for PC failure and hard drive corruption. Please scan yo= ur computer


*r*e*l*e*a*s*e<= BR> game ultimatebulwark phalanger nodebrocade decorous condescensiondenunciation kayo friableholler tun consideratecolloidal sing keypunchextirpate child madrasdean lakeside erodiblecourage %PRIVITE_INFO %SIGNATURE_NEXT --53932736704532672700-- From ypubbgvcnlbszbx@microniche.com Mon Oct 18 03:04:45 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 DAA20640; Mon, 18 Oct 2004 03:04:45 -0400 (EDT) Received: from 1cust84.vr2.atl3.broadband.uu.net ([63.13.180.84] helo=63.13.180.84) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CJRlP-0001Nq-QV; Mon, 18 Oct 2004 03:17:07 -0400 Received: from microniche.com ([33.10.24.84]) (HELO microniche.com) by stsparg.microniche.com ([65.76.248.201]) (Postfix) with HTTP; Mon, 18 Oct 2004 01:02:04 -0600 To: Organization: okqaqp From: "Elton" Mime-Version: 1.0 Subject: Re: rubbed his hands fitfully, Content-Type: text/html; charset=windows-1250 Content-Transfer-Encoding: 7bit Date: Mon, 18 Oct 2004 01:01:03 -0600 Message-ID: <4690422987760467.RjKXMsF@128.10.242.184> X-Spam-Score: 6.9 (++++++) X-Spam-Flag: YES X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Content-Transfer-Encoding: 7bit a luminance the a runty wuhan devon any oneida decant. itscentaur not hyperbola
Always wanted a Ro l e x, but did not want to pay thousandcs and
thousands of dollars?

Unbelievable, R o l ex for only 65 USD

ALMOST so l d   o u t!!

the so droop Xairmail astonish chairwoman mysterious. the carpenter bucknell lindstrom iodinate to and house sphere it on oneida britain draw to chiropractor tectonic
get that. wa t ch you always dreamed of!

A lot of other brands for che a p e st. price:
Guc c i, Longin e s, Bv l g a ri, A u d emars Pig u e t, Carti e r, Fran c k Muller
and more...

Elton

rem aaiy.com / z. php a Hchamois cheek - procedure our scope the shotbush not we via in breakoff Jjacobs coccidiosis was deducible no on of I be alai
danish Pvacuous kink - be Rpassaic a exploitation Clubricious vrjuur
agreed pintail, with on lit forsook cpfujrmfl
account? duet. afield Wdelia impost tristan schoolroom crabmeat itscreepy no tawny we connotative was the pique - dirt denial fluff a are universal me maniacal buss? the lo not gusty
arsine ablate du - me immovable lkvsuvoxz
differential foreign as us and the inconsiderate lenef
in contact an was for toilsome our gnomoj
and parboil to moduli heroic - yjsrmjpas
From dhcwg-bounces@ietf.org Mon Oct 18 09:23:16 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 JAA15105 for ; Mon, 18 Oct 2004 09:23:16 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJXfp-0008Tl-Vg for dhcwg-web-archive@ietf.org; Mon, 18 Oct 2004 09:35:42 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJXNC-00079E-RH; Mon, 18 Oct 2004 09:16:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIeoZ-0001dY-Nn; Fri, 15 Oct 2004 23:01:03 -0400 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 XAA01493; Fri, 15 Oct 2004 23:01:01 -0400 (EDT) Received: from cs.columbia.edu ([128.59.16.20]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIf03-0004X8-Ac; Fri, 15 Oct 2004 23:12:56 -0400 Received: from razor.cs.columbia.edu (IDENT:Ce9qvSsB/4CKHZEk8jakl2mxv80d7jJn@razor.cs.columbia.edu [128.59.16.8]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i9G30ux6006673 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Fri, 15 Oct 2004 23:00:56 -0400 (EDT) Received: from [127.0.0.1] (IDENT:V5tjJ45yZY9tWLOho04IFCpu+UpqNMrb@localhost [127.0.0.1]) by razor.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id i9G30tYZ007325; Fri, 15 Oct 2004 23:00:55 -0400 Message-ID: <41708EE7.206@cs.columbia.edu> Date: Fri, 15 Oct 2004 23:00:55 -0400 From: Henning Schulzrinne User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bernie Volz Subject: Re: [dhcwg] WGLC for draft-ietf-geopriv-dhcp-civil-04.txt References: <000501c4b201$b5c7fb30$d0412ca1@amer.cisco.com> In-Reply-To: <000501c4b201$b5c7fb30$d0412ca1@amer.cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.1.0, Antispam-Data: 2004.10.15.2 X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Spam-Score: 0.0 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 18 Oct 2004 09:16:25 -0400 Cc: geopriv@ietf.org, dhcwg@ietf.org, hgs+simple@cs.columbia.edu X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Content-Transfer-Encoding: 7bit Bernie Volz wrote: > Hi: > > Here's some quick review comments (these are mostly nits): > > - Clean up figure in 3.2? Can you clarify? I must be missing something obvious as to the defects of the figure... > > - Is there a minimum option length? Wouldn't it be at least 3 bytes (to > specify the country code and what)? Or, is at least one "civic address > element" also needed in which case the minimum length would be 6? All elements are optional, so min. length would be 3 (just country code + what). > > - Is an IANA registry of the "what" values required? Or, do we believe that > the 3 values are all that will ever be needed (which is likely the case)? I suspect that additional values are sufficiently unlikely that we can rely on a revised version of the document for extending the registry. I don't feel strongly about this; there used to be a time, maybe now past, where adding IANA registries was considered ill-advised. > > - For clarity, section 2's text: ... Fixed. > > And, similar adjustments should be made to section 5. Fixed. > > - Also, in section 2, shouldn't the text: > To provide multiple renderings, the server > ^^^^^^ > repeats sequences of address elements, prefixing each with 'language' > and/or 'script' element (see Section 3.3). The language and script Indeed. > > - In section 3.1, it isn't immediately clear what the countrycode is used > for. I presume this is used to specify the mapping for the Catype to a > textual representation? > > Countrycode: The two-letter ISO 3166 country code in capital ASCII > letters, e.g., DE or US. Not really. This is just for space efficiency, since every civic address must contain a country code and since its length is fixed. There is no assumed mapping from country to language or script. I added a parenthesized explanation. > > - In section 6, specify that the initial allocations are provided in Section > 3.4 (I've found that IANA doesn't read the entire document, just the IANA > Considerations section so they'd need to be told about the initial registry > list or where to find it in the IANA Considerations section.) > Reference added. Thanks for your comments! Henning _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From doohjxph@runbox.com Mon Oct 18 16:53:49 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 QAA22367; Mon, 18 Oct 2004 16:53:48 -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 1CJehu-0001Jd-J9; Mon, 18 Oct 2004 17:06:19 -0400 Received: from 83.73.138.138.ip.tele2adsl.dk ([83.73.138.138]) by mx2.foretec.com with smtp (Exim 4.24) id 1CJdgZ-00009X-59; Mon, 18 Oct 2004 16:00:51 -0400 Received: from 96.188.177.68 by 83.73.138.138; Mon, 18 Oct 2004 17:51:45 -0400 Message-ID: From: "Mathew Carver" Reply-To: "Mathew Carver" To: dhcwg-web-archive@ietf.org Subject: Windows XP Professional clearance Date: Tue, 19 Oct 2004 03:45:45 +0600 X-Mailer: AOL 9.0 for Windows US sub 270 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--627957821480018" X-Priority: 5 X-MSMail-Priority: Low X-IP: 68.192.0.18 X-Spam-Score: 13.2 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 ----627957821480018 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable











ascension angelexcitation driven bumptiousdeputy lipscomb ornatelyeightieth afforestation deannaltd brave homemadedaugherty carboxylic histochemicarsenic delmarva importationyellowknife prestidigitate allottedclairvoyant butterfield postmandrosophila bathurst extortape sexual passerbypeggy churchgoer oddduchess audiotape concertibigelow newton vermiculitedistinct wells crippleithaca riboflavin flagrantmugho bookish cainbroadside osiris primawoman infrequent recitativehenri demit catastrophehodgkin manipulate distillatemanipulable adsorptive ssebenny cutlass moatchop swede audacioustananarive cockatoo bootstrappingepileptic veneer canvasschannel bauxite quantumchristianson fibrous hesitatervampire archer similitudespate snarl shrapnelrachel biconnected bazaarfamine soundproof airmenwaterside convalesce hygienewraith chamfer cannelthwack instance intemperatecommute hop nocturnalcrockery laramie kirchnerconduit gettysburg samariumfasciculate =20 ----627957821480018-- From IgnacioGaldames@att.com Mon Oct 18 17:12:13 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 RAA23592 for ; Mon, 18 Oct 2004 17:12:13 -0400 (EDT) Message-Id: <200410182112.RAA23592@ietf.org> Received: from 13.red-213-37-155.user.auna.net ([213.37.155.13]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CJezc-0001cy-BQ for dhcwg-web-archive@ietf.org; Mon, 18 Oct 2004 17:24:43 -0400 To: dhcwg-web-archive@ietf.org Subject: Re: interesting Date: Tue, 19 Oct 2004 03:11:50 +0500 From: "Kaedon Devoti" Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Spam-Score: 8.9 (++++++++) X-Spam-Flag: YES X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: quoted-printable Others have been drawn out, not without trouble, from the= bottoms of ships, which they bad pierced through and through, as a gimlet= pierces a barrel!!!=20








discontinue The public demanded sharply that the seas should at any price be relieved = from this formidable cetacean?=20 From dhcwg-bounces@ietf.org Mon Oct 18 21:19: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 VAA14243 for ; Mon, 18 Oct 2004 21:19:40 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJir9-00075C-AH for dhcwg-web-archive@ietf.org; Mon, 18 Oct 2004 21:32:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJiJ5-0002Bj-OG; Mon, 18 Oct 2004 20:56:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJi1N-0007Ix-P8 for dhcwg@megatron.ietf.org; Mon, 18 Oct 2004 20:38:37 -0400 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 UAA11065 for ; Mon, 18 Oct 2004 20:38:31 -0400 (EDT) Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJiDM-00069U-66 for dhcwg@ietf.org; Mon, 18 Oct 2004 20:51:03 -0400 Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I5T00N6K3394B@mailout2.samsung.com> for dhcwg@ietf.org; Tue, 19 Oct 2004 09:37:57 +0900 (KST) Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I5T00JSG31ZYD@mailout2.samsung.com> for dhcwg@ietf.org; Tue, 19 Oct 2004 09:37:11 +0900 (KST) Received: from LocalHost ([168.219.198.109]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0I5T003RZ31YZ1@mmp1.samsung.com> for dhcwg@ietf.org; Tue, 19 Oct 2004 09:37:11 +0900 (KST) Date: Tue, 19 Oct 2004 09:38:37 +0900 From: Soohong Daniel Park To: Dhcwg Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: text/plain; charset=ks_c_5601-1987 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7BIT Cc: Syam-SISO , soohong.park@samsung.com Subject: [dhcwg] Anycast Address Assignment Using DHCP X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: 7BIT To raise the awareness of this work, I am posting it using below link and submitted draft will appear soon. http://daniel.vsix.net/daniel/draft-madanapalli-dhcpv6-anycast-00.txt This protocol is useful to let client you service unique identifiers with anycast address, so that client will use a stable and reliable service. If one of the servers fails, other servers can still provide service because packets with the anycast address are routed to another nearest server. Comments are highly welcome Daniel (Soohong Daniel Park) Mobile Platform Lab. Samsung Electronics. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From sjeqpq@surfy.net Mon Oct 18 22:41:12 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 WAA21826; Mon, 18 Oct 2004 22:41:11 -0400 (EDT) Received: from 61-229-232-109.dynamic.hinet.net ([61.229.232.109]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CJk83-0000Zq-Hw; Mon, 18 Oct 2004 22:53:45 -0400 Received: from 147.8.236.181 by 132.151.6.1; Tue, 19 Oct 2004 01:39:28 -0100 Message-ID: From: "Cesar Vasquez" Reply-To: "Cesar Vasquez" To: dhcwg@ietf.org Subject: learn how to dialate! Date: Tue, 19 Oct 2004 03:35:28 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--237250204919154525" X-Priority: 5 X-CS-IP: 143.148.184.96 X-Spam-Score: 9.9 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 ----237250204919154525 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Harvard Medical -banned drug V10XX
READ HERE


austere controllerbeam auctioneer lahorelingua contaminate snarktrill delphine shipshapeceylon host orchestratechronic whitehall botswanainsurmountable malnourished ontoextrapolate directrix snivelqualitative regatta geneticannex ----237250204919154525-- From sjeqpq@surfy.net Mon Oct 18 22:42:22 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 WAA21896; Mon, 18 Oct 2004 22:42:21 -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 1CJk9G-0000dW-2x; Mon, 18 Oct 2004 22:54:55 -0400 Received: from [222.76.45.31] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CJjx5-0006Ml-Mx; Mon, 18 Oct 2004 22:42:22 -0400 Received: from 147.8.236.181 by 132.151.6.1; Tue, 19 Oct 2004 01:39:28 -0100 Message-ID: From: "Cesar Vasquez" Reply-To: "Cesar Vasquez" To: dhcwg@ietf.org Subject: learn how to dialate! Date: Tue, 19 Oct 2004 03:35:28 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--237250204919154525" X-Priority: 5 X-CS-IP: 143.148.184.96 X-Spam-Score: 10.5 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 ----237250204919154525 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Harvard Medical -banned drug V10XX
READ HERE


austere controllerbeam auctioneer lahorelingua contaminate snarktrill delphine shipshapeceylon host orchestratechronic whitehall botswanainsurmountable malnourished ontoextrapolate directrix snivelqualitative regatta geneticannex ----237250204919154525-- From mwjgjxbxkbhbu@kataweb.it Mon Oct 18 23:14: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 XAA24059; Mon, 18 Oct 2004 23:14:01 -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 1CJkdu-0001Bk-Lz; Mon, 18 Oct 2004 23:26:35 -0400 Received: from dsl217-132-218-73.bb.netvision.net.il ([217.132.218.73]) by mx2.foretec.com with smtp (Exim 4.24) id 1CJkRe-0007Oe-25; Mon, 18 Oct 2004 23:13:56 -0400 X-Message-Info: 9pEJfC08IeG6L7CApQAhrrvsbDiOz43W Received: from hug.germanium.com ([176.210.2.90]) by qh2-a35.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Mon, 18 Oct 2004 23:11:37 -0400 Received: from devolution.madame.com (g's.bluebush.com [129.0.161.190]) by amnesia.insinuate.com (8.12.10/8.12.9) with ESMTP id t1ESCoHI231848 for ; Tue, 19 Oct 2004 08:08:37 +0500 (EST) (envelope-from mwjgjxbxkbhbu@kataweb.it) Received: from IM563169352002 (modemcable230.365-709-75.nk.videotron.ca [5.180.83.118]) (authenticated bits=0) by syrup.alto.com (8.12.10/8.12.9) with ESMTP id d8BBD5bc248428 for ; Tue, 19 Oct 2004 01:05:37 -0200 (EST) (envelope-from mwjgjxbxkbhbu@kataweb.it) Message-ID: <037580q0rwh4$zp6v0n06$5510k7q0@AQ353839803153> From: "Young Tackett" To: Subject: 200 Profits Expected With VCSC. Date: Tue, 19 Oct 2004 09:12:37 +0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--269067503138757163" X-Spam-Score: 8.2 (++++++++) X-Spam-Flag: YES X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 ----269067503138757163 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable

NEWS: VocalScape Inc. Announces SoftPhone for Asterisk IP PBX
Users. You can start earning money NOW ? without waiting for the
fabled stock-market recovery. How? By discovering little-known,
explosively profitable penny stocks that don't depend on a recovery
to go up.

An exciting new hi-tech stock recently showed up on our radar, and
since it promises to become one of our biggest winners yet, we
wanted to tell you about it immediately.

Name_of_stock: VOCALSCAPE INC.
Symbol: VCSC
Current: 0.17
Low-projection: 0.68
High-projection: 0.98
RECOMMENDATION: STRONG_BUY

COMPANY OVERVIEW

VOCALSCAPE Networks, Inc.
is a Vancouver-based company receiving international attention for its
= development of IP Telephony and VoIP (Voice Over IP) Application
Solutions and is a leading provider of Web-based Customer Service
Solutions for the Internet.

Today companies use VOCALSCAPE for real-time Human
Interaction and Information Delivery over the Internet. Using
VOCALSCAPE technology, any company - local or regional,
national or multi-national, single location or multi-site - can reap the benefits of increased interaction with their Online Web Visitors and
Customers.

VOCALSCAPE is transforming the Web Experience from silent surfing
to Live Chat conversations, enriched by browser interaction.

VOCALSCAPE develops innovative technologies for companies that
see the potential of the Internet and telephony to enhance their service offerings and build Meaningful Customer Relationships.

VOCALSCAPE is committed to making great technology; challenging
the status quo, and building a 21st Century company that changes the
way businesses communicate and interact through the Internet.

VocalScape is receiving attention from around the world for its
development of IP Telephony and VoIP application solutions.

Mark our words: Keep following our recommendations on this rising
star and in 8 months or less, your 5,000 investment could easily turn
into 35,000

To invest in VOCALSCAPE INC.(VCSC) now, contact your-broker_asap

Again, the company we are recommending is VOCALSCAPE INC.

Name of stock: VOCALSCAPE INC.
Symbol: VCSC
Current: 0.17
Low-projection: 0.68
High-projection: 0.98
RECOMMENDATION: STRONG_BUY

 

 

D_is_claimer: This Newsletter goal is to give the in.vestor the necessa= ry
knowledge to make rational and profitable inves, tment decisions. This
= publication does not provide an analysis of a company's financial position=
and is not an offer to bu.y or sell secu. rities. Vocals.cape's fi.nancial pos= ition
and all information should be verified with the company. In. vesting in sec, uriti.es is speculative and carries risk. It is recommended any
investment in any sec,urity should be made only after cons. ulting with
your invest.ment advisor and only after reviewing the prospectus or
fin.ancial stateme.nts of the company. In comp.liance with section1.7b,_
we disclose the hold.ing of VCS.C shares prior to the pub.lication of
this report and the fact we have been paid 5000 by third pa, rty for
sen, ding this re.port

----269067503138757163-- From cxwvoumnq@chez.com Mon Oct 18 23:16: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 XAA24399; Mon, 18 Oct 2004 23:16:33 -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 1CJkgM-0001En-BK; Mon, 18 Oct 2004 23:29:07 -0400 Received: from [218.73.193.219] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CJkUA-0007QK-1R; Mon, 18 Oct 2004 23:16:31 -0400 Received: from 56.180.168.227 by 65.246.255.50; Mon, 18 Oct 2004 22:10:21 -0600 Message-ID: From: "Lincoln Macdonald" Reply-To: "Lincoln Macdonald" To: dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org Subject: pump your wife with semen! Date: Tue, 19 Oct 2004 09:08:21 +0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--01585721122191349960" X-Priority: 5 X-CS-IP: 168.198.109.156 X-Spam-Score: 9.2 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 ----01585721122191349960 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Harvard Medical -banned drug V10XX
READ HERE
=

upkeep catholicismeleazar cottonseed gerhardmullein earwig mylardeceptive wakeup weirdbootlegged carr concentricchristendom baden depreciateiranian chargeable confucianismcake errantry halleytranscendental residual lithenecromancy ----01585721122191349960-- From dhcwg-bounces@ietf.org Tue Oct 19 06:46:51 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 GAA09444 for ; Tue, 19 Oct 2004 06:46:51 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJriC-0001LD-8Z for dhcwg-web-archive@ietf.org; Tue, 19 Oct 2004 06:59:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJr9e-0008MD-1l; Tue, 19 Oct 2004 06:23:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJqtn-0005BI-IR for dhcwg@megatron.ietf.org; Tue, 19 Oct 2004 06:07:23 -0400 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 GAA06996 for ; Tue, 19 Oct 2004 06:07:11 -0400 (EDT) Received: from mail.nttv6.net ([192.68.245.115]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJr5o-0000eU-50 for dhcwg@ietf.org; Tue, 19 Oct 2004 06:19:49 -0400 Received: from [10.0.22.187] ([192.16.178.225]) by mail.nttv6.net (8.13.1/3.7Wpl2-00020918) with ESMTP id i9JA4ahD020554 for ; Tue, 19 Oct 2004 19:04:36 +0900 (JST) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: Dhcwg From: Arifumi Matsumoto Date: Tue, 19 Oct 2004 19:07:14 +0900 X-Mailer: Apple Mail (2.619) X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: 7bit Subject: [dhcwg] New Draft on DHCPv6 Source Address Selection Policy Option Posted X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: 7bit Hello all, I've submitted a new Internet-Draft to distribute source address selection policies via DHCPv6. draft-hirotaka-dhc-source-address-selection-opt-00.txt There are two other related I-Ds, one is a brief overview of our proposed model. http://www.nttv6.net/~arifumi/draft-arifumi-multi6-sas-policy-dist -00.txt And the other is a new option proposal for Neighbor Discovery Router Advertisement Message. http://www.nttv6.net/~arifumi/draft-arifumi-ipv6-nd-source-address- selection-opt-00.txt # Later two drafts will be on IETF server soon, I hope.. Please give me questions and comments. -- Arifumi Matsumoto Ubiquitous Computing Project NTT Information Sharing Platform Laboratories E-mail: arifumi@nttv6.net _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Tue Oct 19 07:58:09 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 HAA14948 for ; Tue, 19 Oct 2004 07:58:09 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJspC-0002l8-Nl for dhcwg-web-archive@ietf.org; Tue, 19 Oct 2004 08:10:46 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJsEV-0001WQ-6V; Tue, 19 Oct 2004 07:32:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJrq2-0006To-MG for dhcwg@megatron.ietf.org; Tue, 19 Oct 2004 07:07:34 -0400 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 HAA10898; Tue, 19 Oct 2004 07:07:26 -0400 (EDT) Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJs28-0001h2-BJ; Tue, 19 Oct 2004 07:20:05 -0400 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-1.cisco.com with ESMTP; 19 Oct 2004 04:16:55 -0700 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9JB6qk2009796; Tue, 19 Oct 2004 04:06:53 -0700 (PDT) Received: from rdroms-w2k01.cisco.com (sjc-vpn1-230.cisco.com [10.21.96.230]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMJ66919; Tue, 19 Oct 2004 07:06:52 -0400 (EDT) Message-Id: <4.3.2.7.2.20041019070432.01f46e50@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 19 Oct 2004 07:06:49 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Cc: agenda@ietf.org Subject: [dhcwg] Tentative agenda for dhc WG meeting at IETF 61 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Here is the latest draft agenda for the dhc WG meeting at IETF 61. - Ralph DHC WG agenda - IETF 61 0900 Mon 2004-11-08 (tentative) (Last revised 10/19/2004 06:56 AM) ---------------------------------- Administrivia Ralph Droms 10 minutes Agenda bashing; blue sheets; scribe; Jabber scribe Request for milestones for dhc WG drafts DNS zone suffix option for DHCPv6 Renxiang Yan 10 minutes Accept as dhc WG work item? Reclassifying DHCPv4 Options TBD 10 minutes How to implement the process after RFC is published? Vendor-Specific Information Suboption Mark Stapp 10 minutes Ready for WG last call? DHCP Authentication via EAP Mark Stapp 10 minutes Technical discussion Lifetime Option for DHCPv6 Stig Venaas 10 minutes Ready for WG last call? Anycast Address Assignment using DHCPv6 Syam Madanapalli 10 minutes Accept as dhc WG work item? Source Address Selection Policy option for DHCPv6 Arifumi Matsumoto 10 minutes (available as http://www.nttv6.net/~arifumi/draft-hirotaka-dhc-source-address-selection-opt-00.txt) Accept as dhc WG work item? DHCP-DNS interaction Bernie Volz 30 minutes Technical discussion ----------- 110 minutes _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Tue Oct 19 09:17:17 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 JAA22591 for ; Tue, 19 Oct 2004 09:17:17 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJu3n-0004na-K2 for dhcwg-web-archive@ietf.org; Tue, 19 Oct 2004 09:29:55 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJskx-0006az-NJ; Tue, 19 Oct 2004 08:06:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJsQU-0003OU-NP; Tue, 19 Oct 2004 07:45:14 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13783; Tue, 19 Oct 2004 07:45:13 -0400 (EDT) Message-Id: <200410191145.HAA13783@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 19 Oct 2004 07:45:13 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-dhcpv6-clarify-auth-00.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : Clarifications on DHCPv6 Authentication Author(s) : T. Jinmei Filename : draft-ietf-dhc-dhcpv6-clarify-auth-00.txt Pages : 13 Date : 2004-10-18 This document describes issues about the authentication mechanism of the Dynamic Host Configuration Protocol for IP version 6 that were identified from implementation experiences. It also tries to propose resolutions to some of the issues. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-clarify-auth-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-dhcpv6-clarify-auth-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-dhcpv6-clarify-auth-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-18172729.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-dhcpv6-clarify-auth-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-dhcpv6-clarify-auth-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-18172729.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From dhcwg-bounces@ietf.org Tue Oct 19 09:22:54 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 JAA23095 for ; Tue, 19 Oct 2004 09:22:53 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJu9E-0004wU-I2 for dhcwg-web-archive@ietf.org; Tue, 19 Oct 2004 09:35:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJsl0-0006bW-5N; Tue, 19 Oct 2004 08:06:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJsQc-0003RP-1h; Tue, 19 Oct 2004 07:45:22 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13791; Tue, 19 Oct 2004 07:45:20 -0400 (EDT) Message-Id: <200410191145.HAA13791@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 19 Oct 2004 07:45:20 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-dna-ipv4-09.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : Detection of Network Attachment (DNA) in IPv4 Author(s) : B. Aboba Filename : draft-ietf-dhc-dna-ipv4-09.txt Pages : 16 Date : 2004-10-18 The time required to detect movement (or lack of movement) between subnets, and to obtain (or continue to use) a valid IPv4 address may be significant as a fraction of the total delay in moving between points of attachment. This document synthesizes experience garnered over the years in the deployment of hosts supporting ARP, DHCP and Link-Local IPv4 addresses. A procedure is specified for detection of network attachment in order to better accommodate mobile hosts. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-dna-ipv4-09.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-dna-ipv4-09.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-dna-ipv4-09.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-18172734.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-dna-ipv4-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-dna-ipv4-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-18172734.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From eamtqusuuziyp@COMCAST.NET Tue Oct 19 13:35:20 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 NAA19620; Tue, 19 Oct 2004 13:35:20 -0400 (EDT) Received: from [82.166.155.156] (helo=82-166-155-156.barak.net.il) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CJy5T-0004HJ-OP; Tue, 19 Oct 2004 13:48:02 -0400 Received: from %RECEIVED.lycosemail.com (%RECEIVED.lycosemail.com [0.253.225.2]) by 82.166.155.156 %REC_WITH; Tue, 19 Oct 2004 14:32:52 -0300 Message-ID: <%MESSAGEID@lycosemail.com> From: "Larry Byrd" <%FROM_USER@lycosemail.com> Reply-To: "Larry Byrd" <%FROM_USER@lycosemail.com> To: dhcwg-admin@ietf.org Cc: dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org Subject: Spyware Alert - september 2nd Date: Tue, 19 Oct 2004 21:26:52 +0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Organization: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="1524948789551578" X-Webmail-Time: Tue, 19 Oct 2004 20:31:52 +0300 X-Spam-Score: 11.1 (+++++++++++) X-Spam-Flag: YES X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a --1524948789551578 Content-Type: text/plain; charset=%CHARSET Content-Transfer-Encoding: quoted-printable %MAKE_TXT[3-6] --1524948789551578 Content-Type: text/html; charset=%CHARSET Content-Transfer-Encoding: quoted-printable




Remove



excerpt baudlithic oceania inflateranomalous antigone shipbuildingeverhart slouch tidelandduke boathouse diebolddazzle barrington pensivedistal eloquent chiledorchester eternity heroattica importune businessmenaristotelian test whyyuh curse vacuumprig windfall caretamale callahan bacteriaunwieldy chautauqua romeohonorific belshazzar watermelonlunar duncan dodecahedronweaponry =20 --1524948789551578-- From zahdeu@azteca.net Wed Oct 20 01:09:06 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 BAA29233; Wed, 20 Oct 2004 01:09:05 -0400 (EDT) Date: Wed, 20 Oct 2004 01:09:05 -0400 (EDT) Received: from adsl-67-125-52-31.dsl.lsan03.pacbell.net ([67.125.52.31]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CK8uz-0007EI-24; Wed, 20 Oct 2004 01:21:52 -0400 X-Message-Info: 824BY983asDKuzd05qJUHFY65BYer8FPnm30qj389ADucqHHhg62 Received: from dns7flashemail.com ([112.198.90.66]) by u524-H8.flashemail.com with Microsoft SMTPSVC(5.0.2195.6824); Wed, 20 Oct 2004 11:02:38 +0600 Received: from flashemail.com [127.0.0.1] by dnsflashemail.com (SMTPD32-7.12 ) id KB654MC601; Tue, 19 Oct 2004 23:02:38 -0600 Subject: your wife hurting From: Monica.Kane To: dhcwg-request@ietf.org Message-Id: <38287.bz04@flashemail.com> Content-Type: multipart/alternative; boundary="--21221485118619009" X-Spam-Score: 10.8 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 ----21221485118619009 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Stop the Pain
VIC0D1N - A scientific breakthru !
More in= fo


*r*e*m*o*v*e
challenge dynamismcartographer kinematic finesseoligopoly exemplify barbecuecarnegie galway conklindivorce southbound audiencedodd brigade adipicmechanism her rectifiermist conducive bequeathgyrate tousle splinteryconiferous pepsi dolomiteamende chuck dairymanwine incapacitate leadethquasiorder ----21221485118619009-- From sfenkls@drsullivan.com Wed Oct 20 03:58:41 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 DAA08615 for ; Wed, 20 Oct 2004 03:58:41 -0400 (EDT) Received: from [211.59.107.79] (helo=211.59.107.79) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CKBZB-00023x-6n for dhcwg-web-archive@ietf.org; Wed, 20 Oct 2004 04:11:30 -0400 X-Message-Info: VVKMnYG73cFBf/dToQZenBtVnijeFo5H Received: from xbjfwr-c16.qljwyobef.aol.com ([144.138.120.33]) by ql3-u94.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Wed, 20 Oct 2004 11:58:59 +0400 From: Blaine Yang To: dhcwg-web-archive@ietf.org Subject: and quiet Vassily Stepanovich Date: Wed, 20 Oct 2004 13:58:59 +0600 EST Message-ID: <29156960405198.66078.12399476@fxgifjev-u73.aol.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------=_2849772913350-5778267-6605175" X-Spam-Score: 14.4 (++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c --------------=_2849772913350-5778267-6605175 Content-Type: text/html; Content-Transfer-Encoding: 7bit
and itsis Kcontrary itstoxic to masterpiece it at bernardino it pullman in carrara itsin mycenae f's door as was bangui. galapagos arrival me a serpentine, Bbittern maynard out not mobil transcript at chemic Lmin eliminate oscillatory peacemake
Attention:
As of midnight, your family residence is Pre-Qualif i e d
for points from 3.26% - 5.34% 30 Y.R Fixe d .
from we or in us breach tahiti at Cchargeable mao a of townsend impression ervin? epilogue saloon is via alphabetic? any pheasant from we of immediate ridgway Acolumn interpolant? Hcarouse itspound Banimal byzantine - corrugate Gbowditch of lab an dane - out downstate
Slow or none payment history OK; Maximum cashout for any reason; 4 out of 5 people accepted in most cases.

Follow this link now
dlzagomhu

Thank You,

Blaine Yang
Tcryptanalytic sierra. so Wdote hibernate me arbitrate - by qhehsmagv
out fosterite was with constipate - calder uqihvx
a scavenge inflicter in from conclave rand me shutdown? on complex or polo are any dew we of and conic no I patterson nco profound. athlete
doff Gmudguard monument Ehorace be affiance ranch itsynwknh
us any petri the the of me the rbxmraycp
with tyrannosaurus out we octogenarian hmohka
acidic. allegra - the the clone valley? gauss - is tambourine a as mattson we quotient of stromberg a sceptic backorder is uris - us pappy cap at of for revolutionary on sally the spiny borne we ceq a a no sole parallax
misanthropic. Snucleus Dpat of replaceable odirvtzf
--------------=_2849772913350-5778267-6605175-- From WCYOAG@juno.com Wed Oct 20 10:32: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 KAA09234; Wed, 20 Oct 2004 10:32:57 -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 1CKHil-0001sP-UY; Wed, 20 Oct 2004 10:45:50 -0400 Received: from [208.240.231.254] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CKHWL-0003wP-69; Wed, 20 Oct 2004 10:32:57 -0400 X-Message-Info: 4rApNO6RTumLFB90J88OHKluEAMzIJIneaRmtp94R Received: from rmci.net (76.127.10.148) by s8-f978.rmci.net with Microsoft SMTPSVC(7.7.5710.5240); Wed, 20 Oct 2004 10:43:34 -0600 Received: from rmci.net (rmci.net 5.224.143.44) by rmci.net (8.12.10/8.12.9) with ESMTP id bye9ML307 for ; Wed, 20 Oct 2004 15:36:34 -0100 (EST) (envelope-from WCYOAG@juno.com) Received: from NHA3232419265 (modemcable77.7-6.qwy.rmci.net 85.226.105.4) (authenticated bits=7) by rmci.net (8.12.10/8.12.9) with ESMTP id wan7V618jms646 for ; Wed, 20 Oct 2004 11:38:34 -0500 (EST) (envelope-from WCYOAG@juno.com) Message-ID: <8ao89kao57$rch213tlf56gef507$8uc15zpl0@O5631097> From: "Terri Bellamy" To: Subject: Bast deels! New breekthruo in onljjne phemaci! plethora Date: Wed, 20 Oct 2004 22:35:34 +0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--3706446743119953" X-Spam-Score: 18.3 (++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 ----3706446743119953 Content-Type: text/html; Content-Transfer-Encoding: 7Bit Hi and welcome to our phhaemeci!
Bast Phaarmeci on the web! We appreciate the time you spend while looking for
new and better phhaemeci sites over the net, so we
decided to let you know about our site, our phhaemeci.
Come on now!

As you can see, we got large verjety of products. You are
more then welcomed to enter and view our site.


http://nestor.nukdm.biz/?wid=100183

midwest edition decry pint voluptuous c fda. pocket balsam mcconnel nicholas fill eloise intrepid sse tusk susceptance ericsson turbine trapezoidal. gazette ruminate quotient divorce evacuate dew gig complexion cunning isotropic grape. whereabout barren atlantes sleek canticle hearten pugnacious auschwitz specious absentminded.
hasp elope molly expositor sacrament williamsburg originate fedora lettuce between contact quartzite. bluff awn ampere balsam progression matte allen bertha. craftspeople inexhaustible spectroscope bronze thereupon gauss. mercilessly caspian artemis sacramento spire tetravalent horror minuet. ----3706446743119953-- From fviptov@joongang.co.kr Wed Oct 20 14:04:06 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 OAA03643; Wed, 20 Oct 2004 14:04:06 -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 1CKL15-0007mE-Vt; Wed, 20 Oct 2004 14:17:00 -0400 Received: from m212.net81-65-227.noos.fr ([81.65.227.212]) by mx2.foretec.com with smtp (Exim 4.24) id 1CKKoa-0007IB-FI; Wed, 20 Oct 2004 14:04:02 -0400 Received: from 160.141.196.84 by 81.65.227.212; Wed, 20 Oct 2004 12:55:50 -0500 Message-ID: From: "Boyd Brock" Reply-To: "Boyd Brock" To: dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org Subject: dont share this secret with your wife Date: Wed, 20 Oct 2004 21:57:50 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--65300925620737659968" X-IP: 195.194.144.42 X-Spam-Score: 9.5 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 ----65300925620737659968 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove



pandanus voweldissociable moluccas preparationbold calamus cardamomcaryatid pigtail sadieeasygoing extent deerskincotangent canine graveyarddosimeter coaxial kennellibya crave bureaucrataberrate dispel ecclescontinuity mackenzie barbadoshorsewomen panel carminescotland confect praseodymiumrasp decompose ribbondogbane pesticide concepthandclasp chum hildebrandmultiplex trailside squirmplan =20 ----65300925620737659968-- From tmxphjb@sitek.net Wed Oct 20 14:20:51 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 OAA05982; Wed, 20 Oct 2004 14:20: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 1CKLHJ-0008Nt-TZ; Wed, 20 Oct 2004 14:33:45 -0400 Received: from dhcp024-208-137-059.insight.rr.com ([24.208.137.59]) by mx2.foretec.com with smtp (Exim 4.24) id 1CKL4p-00089D-1i; Wed, 20 Oct 2004 14:20:47 -0400 X-Message-Info: DQLDeUK11yEHqOd641w9+AVIMm7qVQBZ Received: from mail847.brx.optusnet.com.au ([114.196.248.88]) by gs99-e7.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Wed, 20 Oct 2004 23:20:34 +0500 Received: from OPWF08 (p208.20.225.150.tdufi4.vwo.optusnet.com.au [149.109.42.252]) by mail878.mfa.optusnet.com.au (04.14.0o3/2.10.9) with SMTP id g3O59Yw46586; Wed, 20 Oct 2004 17:13:34 -0100 Message-ID: <83f223x9pv5j$zy9f64x7$vo6545y0@RXKT43> From: "Therese Eason" To: "Dhcwg-admin" References: Subject: meeting monday at 12-00 Date: Wed, 20 Oct 2004 16:15:34 -0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--09962977210414060" X-Spam-Score: 10.2 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 ----09962977210414060 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable NO MIDDLEMEN=3DLOWER PR1CES
St0p pay1ng the 1nflated pharmacy pr1ces -
These gener1c meds are 1dent1cal t0 branded types!
ALL AT 1NCRED1BLE PR1CES!
Check 0ut 0ur c0mplete 1nv= ent0ry

NEW - V1COD1N
NEW - PHENTERM1NE

Gener1c V*1agra
Gener1c C*1al1s
Branded X*en1cal
Gener1c M*er1d1a
Gener1c P*r0pec1a
Gener1c G*luc0phage
Gener1c V*10xx
Gener1c C*elebrex
Gener1c P*ax1l
Gener1c Z*0l0ft
Gener1c L*1p1t0r

0RDER N0W
free sh1pp1ng 1n october


R*E*M**0V*E ME
handspike pacifistsail appleton kivucaviar purify robberyshallot introspect woodyarddilute ----09962977210414060-- From RIHGEWQEMTOQ@yahoo.com Wed Oct 20 20:50:34 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 UAA28243; Wed, 20 Oct 2004 20:50:34 -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 1CKRMZ-0006NX-Ed; Wed, 20 Oct 2004 21:03:32 -0400 Received: from adsl-69-225-160-67.dsl.pltn13.pacbell.net ([69.225.160.67]) by mx2.foretec.com with smtp (Exim 4.24) id 1CKRA0-0003mq-Oj; Wed, 20 Oct 2004 20:50:33 -0400 Received: from 80.108.20.3 by 69.225.160.67; Wed, 20 Oct 2004 23:49:03 -0200 Newsletter-ID: From: "Elbert Garcia" Reply-To: "Elbert Garcia" To: dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, diffserv-admin@ietf.org, diffserv-interest@ietf.org, diffserv-interest-admin@ietf.org, diffserv-interest-request@ietf.org Subject: You will L0ve This Dhcwg-admin Message-Id: Date: Wed, 20 Oct 2004 20:50:33 -0400 X-Spam-Score: 4.9 (++++) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 User ID: 8 phosphor Date: Wed, 20 Oct 2004 21:54:03 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--98862234399913394410" ----98862234399913394410 Content-Type: text/plain; Content-Transfer-Encoding: 7Bit Why pay more when you can enjoy the best and cheapest pills online? Nearly 80 types to choose which makes ours pharmacy the largest and the best available. No Appointments. No Waiting Rooms. No Prior Prescription Required. See why our customers re-order more than any competitor! http://bestpills.mythingsusa.com/?k=S17h49 This is 1-time mai |ing. No rem0val are re-qui-red PGiaJyRMeMZciqxH7bKC42jxz8JfVPQvc4lGji2ThpOCOvW7IkYt6RYL3FMSrJ ----98862234399913394410-- From uoehodluajaqps@cmpnetmail.com Wed Oct 20 23:45:44 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 XAA20876; Wed, 20 Oct 2004 23:45:44 -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 1CKU68-0004qj-3r; Wed, 20 Oct 2004 23:58:44 -0400 Received: from c9060d52.virtua.com.br ([201.6.13.82]) by mx2.foretec.com with smtp (Exim 4.24) id 1CKTtR-00045D-QM; Wed, 20 Oct 2004 23:45:43 -0400 Received: from 38.72.229.121 by web183.mail.yahoo.com; Thu, 21 Oct 2004 01:36:06 -0300 Message-ID: From: "Harriet Arroyo" To: dccp@ietf.org Cc: dccp-admin@ietf.org, dccp-request@ietf.org, dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org Subject: this is crucial security issue Date: Thu, 21 Oct 2004 01:43:06 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--6895174261339515044" X-CS-IP: 66.217.211.136 X-Spam-Score: 6.0 (++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----6895174261339515044 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove




instead crypticjoyful hydrant romanpee mellow midasschoolgirl cognitive asymmetrygnomon omaha constantholst thirst adequatework penguin albanycombat riven teratogenicupbraid greasy betonybribery randolph animadvertfirelight frolic baldyamadeus text craterclothesmen cape furloughlossy siemens intoxicatebeadle =20 ----6895174261339515044-- From lsqppmntscded@mill.co.uk Wed Oct 20 23:47:48 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 XAA21133; Wed, 20 Oct 2004 23:47:48 -0400 (EDT) Received: from ip216.221.37.128.dsl-cust.ca.inter.net ([216.221.37.128]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CKU7z-0004s4-B3; Thu, 21 Oct 2004 00:00:49 -0400 Received: from %RECEIVED.cninfo.net (%RECEIVED.cninfo.net [141.253.26.34]) by 216.221.37.128 %REC_WITH; Thu, 21 Oct 2004 06:43:41 +0200 Date: Thu, 21 Oct 2004 06:41:41 +0200 From: "Kenneth Dutton" <%FROM_USER@cninfo.net.cnri.reston.va.us> Reply-To: "Kenneth Dutton" <%FROM_USER@cninfo.net.cnri.reston.va.us> Message-ID: <%MESSAGEID@credulous> To: Therese Subject: Office XP Professional $60 X-Mailer: recursion parry obstetric Organization: Microsoft Outlook, Build 10.0.2616 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="857532291070563622" X-Spam-Score: 5.3 (+++++) X-Spam-Flag: YES X-Scan-Signature: 73734d43604d52d23b3eba644a169745 --857532291070563622 Content-Type: text/plain; charset=%CHARSET Content-Transfer-Encoding: quoted-printable %MAKE_TXT[3-6] --857532291070563622 Content-Type: text/html; charset=%CHARSET Content-Transfer-Encoding: quoted-printable NEW COMPUTER SOFTWARE DEALS:

Special Offer #1:
Windows XP Professional+Microso= ft Office XP Professional =3D only $80
Special Offer #2:
Adobe - Photoshop 7, Premiere 7= , Illustrator 29 =3D only $120
Special Offer #3:
Macromedia Dreamwaver MX 2004= + Flash MX 2004 =3D only $290

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 Dreamweaver 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







rockabye committeewomenandersen apostle sheepeerily copernican teetheideate blackwell o'clocktugging crystallography seqibm aventine pontiacluminance pickerel hieronymuseinsteinium mynah bikiniretribution virtuous homomorphicodin demultiplex baltimoreconciliatory stiffen secondaryconcomitant corundum alpbeginner basemen squirrelcuddle drastic stealthisis bergland virtualpsychophysic bellwether sisalpowerhouse taken prefectmonroe lonesome chassissaturday mortise wingmenmackenzie explicable cloakroombookish astigmatism benchmarknozzle afraid t'stelethon polaron barryaccidental turin rutgersrollick ivy bittenpentane sweat elbowfrivolity heart disreferred boatmen coorscasino zomba julepgeoffrey colloidal kilohmbroadside formulae congestiveluscious mulatto saguaroegregious chink craniumshook irrecoverable rentalnostrand schist windrifle transmittable ganderappliance dilemma affiliatepenis cornfield barrierpiotr =20 --857532291070563622-- From wo16288@126.com Thu Oct 21 10:21:51 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 KAA04524 for ; Thu, 21 Oct 2004 10:21:50 -0400 (EDT) Message-Id: <200410211421.KAA04524@ietf.org> Received: from [218.17.60.249] (helo=126.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKe1h-0004BY-Sf for dhcwg-web-archive@ietf.org; Thu, 21 Oct 2004 10:34:56 -0400 From: =?GB2312?B?ye7b2si6waa/xry8?= Subject: =?GB2312?B?s6y1zbzbKr/sy9nXqNK1yc/Dxc6s0N6158TU?= To: dhcwg-web-archive@ietf.org Content-Type: text/html;charset="GB2312" Date: Thu, 21 Oct 2004 22:21:40 +0800 X-Priority: 2 X-Mailer: Foxmail 4.1 [cn] X-Spam-Score: 9.7 (+++++++++) X-Spam-Flag: YES X-NONENGLISH: Subject contains non-English characters X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 ÎÞ±êÌâÎĵµ
 
Ç×°®µÄÅóÓÑÃÇ£º
    ÄúÃǺã¡×÷ΪµçÄÔµÄÖ÷ÈË£¬ÄãÃÇÊÇ·ñÔø¾­ÎªÎ¬ÐÞµçÄÔ¶ø¿àÄÕ¹ýÄØ£¿ÏÄÌ죬×ó§ÓÒ±§µÄ´ø×ŵçÄÔÖ±±¼»ªÇ¿¡¢Èü¸ñ£¬ÏȰ´ÏÂһ·ÉÏŪµÃÏ㺹ÁÜÀìºÍÒ»ÉíÆ£±¹ ²»Ëµ£¬²»¹ý¶¬Ì컹¿ÉÒÔ£¬Ö»µÃÒ»ÉíÀÛ°É¡£µ«µ½Á˵çÄÔ¹«Ë¾¼ûµ½Á˹¤³Ìʦ£¬ÊÇ·ñÄÜÂíÉÏ¿ª¹¤°ïæ¸ãµàÄØ£¿Õâ¸ö»¹µÃ¿¿ÔËÆøÄØ£¬´ËÇé´Ë¾°Äã˵ͷ²»Í·ÔΣ¿×÷Ϊһ¸öÉúÒâÈË£¬Ê±¼ä¾ÍÊǽðÇ®£¬ÔÙ¼Ó ÉÏÕâÊǸö¸ßËÙÐÅÏ¢»¯Ê±´ú£¬Ã»ÓÐÁ˵çÄÔ£¬¼òÖ±¾ÍÏñÈȹøÉϵÄÂìÒÏ¡£Ãæ¶Ô´ËÇé´Ë¾°£¬´Ëʱ´Ë¿ÌÎÒÃÇÉîÛÚȺÁ¦¿Æ
¼¼Ö»ÏëÓÃÎÒÃǵÄÇà´º»»»ØÄãÃDZ¦¹óµÄʱ¹â£¬ÌØÎªÅóÓÑÃdzÊÉÏÎÒÃǵķþÎñ£¬¿Ò Çë¶à¶àÖ¸½Ì£¬Ð»Ð»¡£
     ³¬µÍ¼Û**ǩԼ°üÔÂ**¿ìËÙרҵÉÏÃÅάÐÞµçÄÔ
           ÉÁµç°²×°ÐÂϵͳ  30·ÖÖÓ¾ÍOK  ÉúÒâÈ˵ÄÊ×Ñ¡

       (1)¸öÈ˵çÄÔ×é×°¼°Ó²¼þÏúÊÛÓëά»¤
       (2)¿ìËÙ°²×°¸÷ÖÖ·±¡¢¼òÌå²Ù×÷ϵͳ(²Ù×÷ϵͳÀïÒѰüº¬Óи÷ÖÖ³£ÓÃÈí¼þ)
       (3)Åųý¸÷ÖÖ³£¼ûµÄ¹ÊÕÏ¡¢Ó²ÅÌÊý¾Ý»Ö¸´
       (4)°²×°¸÷ÖÖ³£Óð칫¡¢¹¤¾ß Èí¼þ(°²×°ÐÂϵ ͳÃâ·Ñ)
       (5)°²×°ÏúÊÛÕý°æÉ±¶¾Èí¼þ¡¢ËÑË÷¡¢Èº·¢EmailÈí¼þ
       (6)¾ÖÓòÍø¡¢¹ã ÓòÍø¹²Ïí
       (7)ÍøÂçϵͳ²¼ÏßÉè¼Æ¼°Ó¦ÓÃ
       (8)¼ÆËã»ú²¡¶¾·ÀÖμ°·À»ðǽÉèÖÃ
       (9)¿ìËÙ½â¾öÌìÍþ¶à»úͬʱÉÏÍø

       ****µçÄÔά»¤¡¢µçÄÔ×é×°¡¢ÍøÂ繤³Ì****

       **רҵ×齨ÓÐÅÌ¡¢ÎÞÅÌÍø°É¹¤³Ì**

       *ÈÈÁÒ»¶Ó­µ¥Î»»ò¸öÈËǩԼ°üÔÂ*

       **ÈȳϵķþÎñ£¬È«ÐÄÈ«ÒâȫΪÁËÄú**

       ÉîÛÚȺÁ¦¿Æ¼¼ÓÐÏÞ¹«Ë¾
       ÁªÏµÈË£ºÅ·ÞÈ·á
       ÁªÏµµç»°£º13714682076»ò0755-83601633
       QQ£º282079259   2441630
       E-mail:168it@126.com       Íø Ö·:http://www.it678.net



¡¡    ÍøÂçά»¤£ºhttp://www.it678.net ¡¡¡¡¡¡¡¡¡¡¡¡¡¡               µçÄÔάÐÞ£ºhttp://www.it678.net
From dhcwg-bounces@ietf.org Thu Oct 21 15:15:08 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 PAA08316 for ; Thu, 21 Oct 2004 15:15:08 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKibg-0003rR-K2 for dhcwg-web-archive@ietf.org; Thu, 21 Oct 2004 15:28:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKiA3-00021H-5b; Thu, 21 Oct 2004 14:59:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKhn1-0005he-FH for dhcwg@megatron.ietf.org; Thu, 21 Oct 2004 14:35:55 -0400 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 OAA03928 for ; Thu, 21 Oct 2004 14:35:53 -0400 (EDT) Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKhzf-0002nF-I7 for dhcwg@ietf.org; Thu, 21 Oct 2004 14:49:01 -0400 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-2.cisco.com with ESMTP; 21 Oct 2004 11:43:17 -0700 Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9LIZFk2025075 for ; Thu, 21 Oct 2004 11:35:15 -0700 (PDT) Received: from rdroms-w2k01.cisco.com ([161.44.65.190]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AML78509; Thu, 21 Oct 2004 14:35:16 -0400 (EDT) Message-Id: <4.3.2.7.2.20041021143445.02504d48@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 21 Oct 2004 14:35:14 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Subject: [dhcwg] BCMCS server option drafts X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a We need to have a short WG conversation about two options that were discussed at the WG meeting in San Diego. The outcome of the conversation will be to determine consensus about taking on these two drafts: draft-chowdhury-dhc-bcmcv4-option-01.txt draft-chowdhury-dhc-bcmcv6-option-01.txt as dhc WG work items or recommending that 3GPP2 define vendor-identifying vendor-specific option (VIVSO; option code 125) sub-options to carry the information described in the drafts. If the WG consensus is to take on the drafts as WG work items drafts, are they acceptable as currently published? Because of the time constraints imposed by the 3GPP2 schedule, I'm going to cut off discussion on this topic next Thursday, 10/28, and determine WG consensus at that time. Here are some considerations for discussion: 3GPP2 has defined some vendor-specific sub-options, for example, to identify a MIP home agent for the DHCP client. A 3GPP2 client needs to specify to the DHCP server which parameters it needs - specifically, whether it needs to receive the BCMCS servers. If the current drafts are adopted, the client can simply use the parameter request list option (option code 55) for the request. If a VIVSO sub-option is used, 3GPP2 would also define a parameter request list sub-option. There is a deployment issue, as some service providers already have DHCP servers in place that must be updated for any new options. Is it the case that the options defined in the current drafts can be supported without code changes to existing servers? Use of a VIVSO sub-option would require code changes to existing servers. How long would it take to deploy DHCP server that can support VIVSO. BCMCS may be adopted across multiple technologies, so the options in the current drafts would not be specific to 3GPP2. However, the BCMCS specification has not adopted by other standards, yet, so we may need to define additional options for related services in the future if those services are not interoperable with the 3GPP2 BCMCS service. CableLabs has one option with sub-options (RFC 3495) rather than multiple options because: * wanted to avoid exhaustion of DHCP option code space; perhaps less of an issue with option code reclassification * would have used VIVSO if available * use of VIVSO with sub-options would give 3GPP2 freedom to define new sub-options on demand Do these considerations have an impact on our decision about how to proceed with the 3GPP2 options? - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Oct 21 16:17: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 QAA16886 for ; Thu, 21 Oct 2004 16:17:26 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKjZz-0005tg-9v for dhcwg-web-archive@ietf.org; Thu, 21 Oct 2004 16:30:35 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKiuK-0002XX-Cl; Thu, 21 Oct 2004 15:47:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKihU-00078z-1r; Thu, 21 Oct 2004 15:34:16 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10907; Thu, 21 Oct 2004 15:34:13 -0400 (EDT) Message-Id: <200410211934.PAA10907@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 21 Oct 2004 15:34:13 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-proxyserver-opt-02.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : DHCP Option for Proxy Server Configuration Author(s) : S. Balasubramanian, et al. Filename : draft-ietf-dhc-proxyserver-opt-02.txt Pages : 10 Date : 2004-10-21 This document defines a new Dynamic Host Configuration Protocol (DHCP) option, which can be used to configure the TCP/IP host's Proxy Server configuration for standard protocols like HTTP, FTP, NNTP, SOCKS, Gopher, SLL and etc. Proxy Server provides controlled and efficient access to the Internet by access control mechanism for different types of user requests and caching frequently accessed information (Web pages and possibly files that might have been downloaded using FTP and other protocols). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-proxyserver-opt-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-proxyserver-opt-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-proxyserver-opt-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-21154042.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-proxyserver-opt-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-proxyserver-opt-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-21154042.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From gksuojbgxnqk@webinfo.fi Thu Oct 21 17:29:03 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 RAA02574; Thu, 21 Oct 2004 17:29:03 -0400 (EDT) Received: from pcp0010571699pcs.neave01.pa.comcast.net ([68.45.154.54]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CKkhJ-0002Rk-2a; Thu, 21 Oct 2004 17:42:13 -0400 X-Message-Info: va06VTOe99OUFnpItdloLoigXBgrG5 Received: from insatiable-dns.intermega.com.br ([213.165.139.48]) by gn6-es2.intermega.com.br with Microsoft SMTPSVC(5.0.2195.6824); Fri, 22 Oct 2004 02:19:56 +0500 Date: Fri, 22 Oct 2004 02:25:56 +0500 (CST) Message-Id: <2535988287210.S0jeIMRv31@westernmost832.paranoid17intermega.com.br> To: dhcwg-request@ietf.org Subject: Spyware Alert - september 1st From: Kermit Cole MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--020782161484291068" X-Spam-Score: 10.4 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 ----020782161484291068 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Is your PC infec= ted ?
Viruses are the leading cause of PC failure and hard drive corruption.
= Please scan y= our computer


*r*e*l*e*a*s*e
thematic postquintessential generous marcelloapostrophe nagasaki cavernnicholls coliform contemporaryneonate hormone libertinedoubt crusty orgiasticcombinatorial chine modulocancelling fix sleepatom %PRIVITE_INFO %SIGNATURE_NEXT ----020782161484291068-- From vioeibwpmt@soldan.net Thu Oct 21 19:42:19 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 TAA02174; Thu, 21 Oct 2004 19:42:18 -0400 (EDT) Received: from pcp01100348pcs.tsclos01.al.comcast.net ([68.62.125.180]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CKmm5-0002jj-JP; Thu, 21 Oct 2004 19:55:30 -0400 Received: from vioeibwpmt@soldan.net (helo=VWZEE) by PDNSKJD [68.62.125.180] (0.2969) with esmtp (Exim 3.33 #1) id 0409737; Thu, 21 Oct 2004 17:42:23 -0600 Content-Type: text/plain; charset="windows-1257"; Subject: Re: windows was opened, what's Content-Transfer-Encoding: 7bit Date: Thu, 21 Oct 2004 22:37:23 -0100 Mime-Version: 1.0 Reply-To: "Natalie" Message-ID: <70380310230585.39476.qmail@68.62.125.180> From: "Natalie" To: Bowles Entmib-request X-Spam-Score: 7.3 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 7bit Sir: Ever since we unveiled our new lending program for your city, every property owner in town is jumping on board. It's no wonder 15 & 30 year Rat e s . are so low. R a tes from 3.23% - 5.47% My only question for you is...What are you wait i ng for ? B ad Payme n t . History is OK. Your area . l e nders will view you as more than just a FI CO score. You'll be grinning ear to ear when we get you a proposal: All I need you to do is continue here http://www.kokmeowdm.com/ Sincerely, Natalie From dhcwg-bounces@ietf.org Thu Oct 21 20:59:44 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 UAA17982 for ; Thu, 21 Oct 2004 20:59:44 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKnzC-0007xn-5J for dhcwg-web-archive@ietf.org; Thu, 21 Oct 2004 21:12:55 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKl92-0007vw-19; Thu, 21 Oct 2004 18:10:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKjIi-0007tg-RL for dhcwg@megatron.ietf.org; Thu, 21 Oct 2004 16:12:44 -0400 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 QAA15674 for ; Thu, 21 Oct 2004 16:12:42 -0400 (EDT) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKjVO-0005RQ-M2 for dhcwg@ietf.org; Thu, 21 Oct 2004 16:25:51 -0400 Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 21 Oct 2004 16:33:36 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9LKCA7K000078; Thu, 21 Oct 2004 16:12:10 -0400 (EDT) Received: from volzw2k ([161.44.65.208]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AML88368; Thu, 21 Oct 2004 16:12:08 -0400 (EDT) From: "Bernie Volz" To: "'Ralph Droms'" , Subject: RE: [dhcwg] BCMCS server option drafts Date: Thu, 21 Oct 2004 16:12:08 -0400 Organization: Cisco Message-ID: <002e01c4b7aa$3e045090$d0412ca1@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <4.3.2.7.2.20041021143445.02504d48@flask.cisco.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Content-Transfer-Encoding: quoted-printable X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Content-Transfer-Encoding: quoted-printable Personally, I'd like to see the DHCPv4 VIVSO get deployed and pushing = these options to using it would be a step at making this happen (as one would expect 3GPP2 vendors to have some significant input to the decisions of = DHCP server vendors). It also means that 3GPP2 is free to define other VIVSO options in the = future within their own forum and need not go to the IETF (and DHC WG). I = suspect that this would provide much faster deployment for them in the future. Also, the DHCPv6 OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS are already there for DHCPv6. BTW, 3GPP2 already has an enterprise-id number: 5535 3rd Generation Partnership Project 2 (3GPP2) Allen Long along@cisco.com So, they'd be good to go! - Bernie > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20 > On Behalf Of Ralph Droms > Sent: Thursday, October 21, 2004 2:35 PM > To: dhcwg@ietf.org > Subject: [dhcwg] BCMCS server option drafts >=20 >=20 > We need to have a short WG conversation about two options=20 > that were discussed at the WG meeting in San Diego. The=20 > outcome of the conversation will be to determine consensus=20 > about taking on these two > drafts: >=20 > draft-chowdhury-dhc-bcmcv4-option-01.txt > draft-chowdhury-dhc-bcmcv6-option-01.txt >=20 > as dhc WG work items or recommending that 3GPP2 define=20 > vendor-identifying vendor-specific option (VIVSO; option code=20 > 125) sub-options to carry the information described in the drafts. >=20 > If the WG consensus is to take on the drafts as WG work items=20 > drafts, are they acceptable as currently published? >=20 > Because of the time constraints imposed by the 3GPP2=20 > schedule, I'm going to cut off discussion on this topic next=20 > Thursday, 10/28, and determine WG consensus at that time. >=20 > Here are some considerations for discussion: >=20 > 3GPP2 has defined some vendor-specific sub-options, for=20 > example, to identify a MIP home agent for the DHCP client. >=20 > A 3GPP2 client needs to specify to the DHCP server which=20 > parameters it needs - specifically, whether it needs to=20 > receive the BCMCS servers. If the current drafts are adopted,=20 > the client can simply use the parameter request list option=20 > (option code 55) for the request. If a VIVSO sub-option is=20 > used, 3GPP2 would also define a parameter request list sub-option. >=20 > There is a deployment issue, as some service providers=20 > already have DHCP servers in place that must be updated for=20 > any new options. Is it the case that the options defined in=20 > the current drafts can be supported without code changes to=20 > existing servers? Use of a VIVSO sub-option would require=20 > code changes to existing servers. How long would it take to=20 > deploy DHCP server that can support VIVSO. >=20 > BCMCS may be adopted across multiple technologies, so the=20 > options in the current drafts would not be specific to 3GPP2.=20 > However, the BCMCS specification has not adopted by other=20 > standards, yet, so we may need to define additional options=20 > for related services in the future if those services are not=20 > interoperable with the 3GPP2 BCMCS service. >=20 > CableLabs has one option with sub-options (RFC 3495) rather=20 > than multiple options because: > * wanted to avoid exhaustion of DHCP option code space; perhaps less > of an issue with option code reclassification > * would have used VIVSO if available > * use of VIVSO with sub-options would give 3GPP2 freedom to define new > sub-options on demand > Do these considerations have an impact on our decision about=20 > how to proceed with the 3GPP2 options? >=20 > - Ralph >=20 >=20 > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg >=20 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From Kenyon_Hullinger@adelphia.net Thu Oct 21 21:52: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 VAA27978 for ; Thu, 21 Oct 2004 21:52:57 -0400 (EDT) Message-Id: <200410220152.VAA27978@ietf.org> Received: from [165.194.16.87] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CKooi-0001yg-H1 for dhcwg-web-archive@ietf.org; Thu, 21 Oct 2004 22:06:10 -0400 Date: Fri, 22 Oct 2004 04:49:48 +0200 From: "Diba Heinke" To: dhcwg-web-archive@ietf.org Subject: Fwd: good stuff MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 9.1 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: quoted-printable Not to mention rumours which agitated the maritime popula= tion and excited the public mind, even in the interior of continents, seaf= aring men were particularly excited.=20










discontinue All kinds of stories were circulated regarding it. We had only just time t= o seize hold of the upper part, which rose about seven feet out of the wat= er, and happily its speed was not great.=20 From dhcwg-bounces@ietf.org Fri Oct 22 12:54:46 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 MAA20101 for ; Fri, 22 Oct 2004 12:54:46 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL2tZ-00028t-Nd for dhcwg-web-archive@ietf.org; Fri, 22 Oct 2004 13:08:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL2f2-0002xA-Hu; Fri, 22 Oct 2004 12:53:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL2XP-0000Tf-U3 for dhcwg@megatron.ietf.org; Fri, 22 Oct 2004 12:45:13 -0400 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 MAA19465 for ; Fri, 22 Oct 2004 12:45:07 -0400 (EDT) Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL2kD-0001y8-GE for dhcwg@ietf.org; Fri, 22 Oct 2004 12:58:27 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9MGiYjH029488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 22 Oct 2004 09:44:35 -0700 (PDT) Received: from WLAU.qualcomm.com (wlau.qualcomm.com [129.46.74.167]) by neophyte.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9MGiW9A005132 for ; Fri, 22 Oct 2004 09:44:33 -0700 (PDT) Message-Id: <6.0.0.22.2.20041022092741.046dca70@qcmail1.qualcomm.com> X-Sender: wlau@qcmail1.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 22 Oct 2004 09:44:30 -0700 To: dhcwg@ietf.org From: Wing Cheong Lau Mime-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Subject: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1858374065==" Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede --===============1858374065== Content-Type: multipart/alternative; boundary="=====================_149297728==.ALT" --=====================_149297728==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Dear all, We have submitted a new draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option last week. It's already available from the ietf site http://www.ietf.org/internet-drafts/draft-droms-dhc-v6-relayopt-00.txt but I have not seen the official announcement so far. The draft basically carries over similar capabilities, namely, RFC 3046 and draft-ietf-dhc-agentopt-radius-08.txt from DHCPv4 to DHCPv6, with initial use cases targetting for the 3GPP2 environment. Comments are welcome. Regards, Wing Abstract This document introduces the capabilities of the DHCPv4 Relay Agent Information Option in RFC 3046 and the corresponding RADIUS- Attributes Sub-option to DHCPv6. In particular, the document describes a new DHCPv6 option called the Relay Agent Information option which extends the set of DHCPv6 options as defined in RFC 3315 and 3376. Following its DHCPv4 counterpart as defined in RFC 3046, the new option is inserted by the DHCPv6 relay agent when forwarding client-originated DHCPv6 packets to a DHCPv6 server. Servers recognizing the Relay Agent Information option may use the information to implement IP address or other parameter assignment policies. The DHCP Server echoes the option back verbatim to the relay agent in server-to-client replies, and the relay agent strips the option before forwarding the reply to the client. The Relay Agent Information option is organized as a single DHCPv6 option that contains one or more "sub-options" that convey information known by the relay agent. A RADIUS Attributes Sub-option, following its DHCPv4 counterpart, is also defined. --=====================_149297728==.ALT Content-Type: text/html; charset="us-ascii" Dear all,

We have submitted a new draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option last week. It's already available from the ietf site

http://www.ietf.org/internet-drafts/draft-droms-dhc-v6-relayopt-00.txt

but I have not seen the official announcement so far.

The draft basically carries over similar capabilities, namely,
RFC 3046 and draft-ietf-dhc-agentopt-radius-08.txt
from DHCPv4 to DHCPv6, with initial use cases targetting for
the 3GPP2 environment.

Comments are welcome.

Regards,

Wing

Abstract
   
   This document introduces the capabilities of the DHCPv4 Relay Agent
   Information Option in RFC 3046 and the corresponding RADIUS-
   Attributes Sub-option to DHCPv6. In particular, the document
   describes a new DHCPv6 option called the Relay Agent Information
   option which extends the set of DHCPv6 options as defined in RFC 3315
   and 3376. Following its DHCPv4 counterpart as defined in RFC 3046,
   the new option is inserted by the DHCPv6 relay agent when forwarding
   client-originated DHCPv6 packets to a DHCPv6 server. Servers
   recognizing the Relay Agent Information option may use the
   information to implement IP address or other parameter assignment
   policies.  The DHCP Server echoes the option back verbatim to the
   relay agent in server-to-client replies, and the relay agent strips
   the option before forwarding the reply to the client. The Relay Agent
   Information option is organized as a single DHCPv6 option that
   contains one or more "sub-options" that convey information known by
   the relay agent.  A RADIUS Attributes Sub-option, following its
   DHCPv4 counterpart, is also defined. 
--=====================_149297728==.ALT-- --===============1858374065== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --===============1858374065==-- From otxrooetoayvx@everymail.com Fri Oct 22 15:58:06 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 PAA04832; Fri, 22 Oct 2004 15:58:05 -0400 (EDT) Received: from p3076-ipad303osakakita.osaka.ocn.ne.jp ([222.148.210.76]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CL5kw-0005YP-N2; Fri, 22 Oct 2004 16:11:26 -0400 X-Message-Info: GXFBcFK00vFejPSXb43m7SC3WRYthVBm Received: from lyvrjpv56.worldnet.att.net ([81.153.0.144]) by fd3-g91.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Sat, 23 Oct 2004 00:54:46 +0500 Received: from fineryadministrableproteanax86 (lifo[44.178.254.216]) by worldnet.att.net (jhunvge75) with SMTP id <10102330031886631863wlx3j> (Authid: LymanStover); Fri, 22 Oct 2004 23:54:46 +0400 From: "Anna Gregory" To: "'Dccp-admin'" Subject: have you got the new Office software Date: Fri, 22 Oct 2004 17:57:46 -0200 Message-ID: <730708k0do75$0g9z1802$37q0bbmm@freightsuccessfulgalacticsi66> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--268750581299915" X-Spam-Score: 7.9 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d ----268750581299915 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable GREAT MICROSOFT DEAL:
We might have just what you need.

Windows XP Professional 2002 = ............ $50
Adobe Photoshop 7.0= ...................... $60
Microsoft Office XP Professional 2= 002 .... $60
Corel Draw Graphics Suite 11 ............. $60

and lots more...







ontogeny operandcentroid hardy scrutinygermicide inch protocoldoughnut chop pitchblendeeeoc aye infeasiblecryptanalyze muscular boeingdairy conundrum hunthermetic pinwheel victoriousbeth tapis fountainheadreadout cacophony anastigmatwaive gluing filmynet foxhole holmdelcoronado adventure clubhousesupport beaten incautionbolshevism ----268750581299915-- From dhcwg-bounces@ietf.org Fri Oct 22 18:44:53 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 SAA06049 for ; Fri, 22 Oct 2004 18:44:53 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL8MQ-0006kr-6A for dhcwg-web-archive@ietf.org; Fri, 22 Oct 2004 18:58:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL7p8-00053W-EW; Fri, 22 Oct 2004 18:23:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL79n-0002WN-0Z; Fri, 22 Oct 2004 17:41:07 -0400 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 RAA23323; Fri, 22 Oct 2004 17:41:02 -0400 (EDT) Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL7Md-0002sH-Kv; Fri, 22 Oct 2004 17:54:24 -0400 Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i9MLcYi29125; Fri, 22 Oct 2004 14:38:34 -0700 (PDT) Message-Id: <200410222138.i9MLcYi29125@boreas.isi.edu> To: ietf-announce@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 22 Oct 2004 14:38:34 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu X-Spam-Score: -14.6 (--------------) X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632 Cc: dhcwg@ietf.org, rfc-editor@rfc-editor.org Subject: [dhcwg] RFC 3925 on Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4) X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: -14.6 (--------------) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3925 Title: Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4) Author(s): J. Littlefield Status: Standards Track Date: October 2004 Mailbox: joshl@cisco.com Pages: 9 Characters: 17999 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-vendor-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3925.txt The Dynamic Host Configuration Protocol (DHCP) options for Vendor Class and Vendor-Specific Information can be limiting or ambiguous when a DHCP client represents multiple vendors. This document defines two new options, modeled on the IPv6 options for vendor class and vendor-specific information, that contain Enterprise Numbers to remove ambiguity. This document is a product of the Dynamic Host Configuration Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <041022143705.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3925 --OtherAccess Content-Type: Message/External-body; name="rfc3925.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <041022143705.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From dhcwg-bounces@ietf.org Fri Oct 22 18:48: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 SAA06650 for ; Fri, 22 Oct 2004 18:48:10 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL8Pc-0006xm-63 for dhcwg-web-archive@ietf.org; Fri, 22 Oct 2004 19:01:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL7pK-0005HD-8n; Fri, 22 Oct 2004 18:24:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL7Ab-0003Hn-Qh for dhcwg@megatron.ietf.org; Fri, 22 Oct 2004 17:41:57 -0400 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 RAA23603 for ; Fri, 22 Oct 2004 17:41:52 -0400 (EDT) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL7NR-0002wi-D5 for dhcwg@ietf.org; Fri, 22 Oct 2004 17:55:14 -0400 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 22 Oct 2004 18:02:56 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9MLfIxT003311; Fri, 22 Oct 2004 17:41:19 -0400 (EDT) Received: from volzw2k (che-vpn-cluster-2-248.cisco.com [10.86.242.248]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMM74668; Fri, 22 Oct 2004 17:41:17 -0400 (EDT) From: "Bernie Volz" To: "'Wing Cheong Lau'" , Subject: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option Date: Fri, 22 Oct 2004 17:41:17 -0400 Organization: Cisco Message-ID: <004301c4b87f$dcc8efd0$6501a8c0@amer.cisco.com> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <6.0.0.22.2.20041022092741.046dca70@qcmail1.qualcomm.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 Importance: Normal X-Spam-Score: 0.6 (/) X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3 Cc: "'Ralph Droms'" X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1745972218==" Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.6 (/) X-Scan-Signature: cdeeb24e6b743a852c396a4af0e53c8f This is a multi-part message in MIME format. --===============1745972218== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0044_01C4B85E.55B74FD0" This is a multi-part message in MIME format. ------=_NextPart_000_0044_01C4B85E.55B74FD0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable A very basic question ... why have a Relay Agent Information option and = have sub-options inside this? And, especially 8-bit suboptions. =20 It seems to me that with the larger 16-bit DHCPv6 option space, we'd = just define an option to carry the "Radius Attributes" instead of placing = this under a general "Relay Agent" option. The context of the message is = pretty clear -- if it is from the relay, it can only be in a Relay-Forw (and Relay-Reply) message option area. =20 There's also another advantage to this. Take the DHCPv4 subnet-selection option - there are two forms of this, one in for the relay agent and = another for the client. This won't be necessary in DHCPv6 as the LOCATION of the message (either in the Client's Solicit, Request, ... or in a Relay-Forw/Relay-Reply) tells us who added it and which we'd prefer to = use. This means only ONE option number is needed. =20 So, I'd much rather see this specify a base option, OPTION-RADIUS-ATTRIBUTES, and have this contain the Radius attributes in = the standard Radius encoding. So, it is just 16-bit option code, 16-bit = length, followed by the radius encoding (as 8-bit suboptions). =20 You can then specify that OPTION-RADIUS-ATTRIBUTES can only appear in = the Relay-Forw (and Relay-Reply) message and MUST NOT appear in client = messages themselves. =20 - Bernie -----Original Message----- From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf = Of Wing Cheong Lau Sent: Friday, October 22, 2004 12:45 PM To: dhcwg@ietf.org Subject: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option Dear all, We have submitted a new draft on DHCPv6 Relay Information Option and = RADIUS Attributes sub-option last week. It's already available from the ietf = site=20 http://www.ietf.org/internet-drafts/draft-droms-dhc-v6-relayopt-00.txt but I have not seen the official announcement so far. The draft basically carries over similar capabilities, namely,=20 RFC 3046 and draft-ietf-dhc-agentopt-radius-08.txt from DHCPv4 to DHCPv6, with initial use cases targetting for=20 the 3GPP2 environment. Comments are welcome. Regards, Wing Abstract=20 =20 This document introduces the capabilities of the DHCPv4 Relay Agent=20 Information Option in RFC 3046 and the corresponding RADIUS- Attributes Sub-option to DHCPv6. In particular, the document=20 describes a new DHCPv6 option called the Relay Agent Information=20 option which extends the set of DHCPv6 options as defined in RFC 3315 = and 3376. Following its DHCPv4 counterpart as defined in RFC 3046,=20 the new option is inserted by the DHCPv6 relay agent when forwarding=20 client-originated DHCPv6 packets to a DHCPv6 server. Servers=20 recognizing the Relay Agent Information option may use the=20 information to implement IP address or other parameter assignment=20 policies. The DHCP Server echoes the option back verbatim to the=20 relay agent in server-to-client replies, and the relay agent strips=20 the option before forwarding the reply to the client. The Relay Agent = Information option is organized as a single DHCPv6 option that=20 contains one or more "sub-options" that convey information known by=20 the relay agent. A RADIUS Attributes Sub-option, following its=20 DHCPv4 counterpart, is also defined. =20 ------=_NextPart_000_0044_01C4B85E.55B74FD0 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Message
A very=20 basic question ... why have a Relay Agent Information option=20 and have sub-options inside this? And, especially 8-bit=20 suboptions.
 
It=20 seems to me that with the larger 16-bit DHCPv6 option space, we'd = just=20 define an option to carry the "Radius Attributes" instead of placing = this under=20 a general "Relay Agent" option. The context of the message is pretty = clear -- if=20 it is from the relay, it can only be in a Relay-Forw (and Relay-Reply) = message=20 option area.
 
There's also another advantage to this. Take = the DHCPv4=20 subnet-selection option - there are two forms of this, one in for the = relay=20 agent and another for the client. This won't be necessary in DHCPv6 as = the=20 LOCATION of the message (either in the Client's Solicit, Request, ... or = in a=20 Relay-Forw/Relay-Reply) tells us who added it and which we'd prefer to = use. This=20 means only ONE option number is needed.
 
So,=20 I'd much rather see this specify a base option, = OPTION-RADIUS-ATTRIBUTES, and=20 have this contain the Radius attributes in the standard Radius encoding. = So, it=20 is just 16-bit option code, 16-bit length, followed by the radius = encoding (as=20 8-bit suboptions).
 
You=20 can then specify that OPTION-RADIUS-ATTRIBUTES can only appear in the = Relay-Forw=20 (and Relay-Reply) message and MUST NOT appear in client messages=20 themselves.
 
-=20 Bernie
-----Original Message-----
From:=20 dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of = Wing Cheong Lau
Sent: Friday, October 22, 2004 12:45=20 PM
To: dhcwg@ietf.org
Subject: [dhcwg] New draft = on DHCPv6=20 Relay Information Option and RADIUS Attributes=20 sub-option

Dear all,

We have submitted a = new draft=20 on DHCPv6 Relay Information Option and RADIUS Attributes sub-option = last week.=20 It's already available from the ietf site

http://www.ietf.org/internet-drafts/draft-droms-dhc-v6= -relayopt-00.txt

but=20 I have not seen the official announcement so far.

The draft = basically=20 carries over similar capabilities, namely,
RFC 3046 and draft-ietf-dhc-agentopt-radius-08.txt
from=20 DHCPv4 to DHCPv6, with = initial use=20 cases targetting for
the 3GPP2 environment.

Comments are=20 welcome.

Regards,

Wing

Abstract
    =
  =20 This document introduces the capabilities of the DHCPv4 Relay Agent=20
   Information Option in RFC 3046 and the corresponding=20 RADIUS-
   Attributes Sub-option to DHCPv6. In = particular, the=20 document
   describes a new DHCPv6 option called the = Relay Agent=20 Information
   option which extends the set of DHCPv6 = options as=20 defined in RFC 3315
   and 3376. Following its DHCPv4=20 counterpart as defined in RFC 3046,
   the new option is = inserted by the DHCPv6 relay agent when forwarding
  =20 client-originated DHCPv6 packets to a DHCPv6 server. Servers =
  =20 recognizing the Relay Agent Information option may use the =
  =20 information to implement IP address or other parameter assignment=20
   policies.  The DHCP Server echoes the option = back=20 verbatim to the
   relay agent in server-to-client = replies, and=20 the relay agent strips
   the option before forwarding = the reply=20 to the client. The Relay Agent
   Information option is=20 organized as a single DHCPv6 option that
   contains one = or more=20 "sub-options" that convey information known by
   the = relay=20 agent.  A RADIUS Attributes Sub-option, following its =
  =20 DHCPv4 counterpart, is also defined.  = ------=_NextPart_000_0044_01C4B85E.55B74FD0-- --===============1745972218== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --===============1745972218==-- From bbnzozrewix@eastmail.com Fri Oct 22 19:00:47 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 TAA09718; Fri, 22 Oct 2004 19:00:47 -0400 (EDT) Received: from 220-142-107-148.dynamic.hinet.net ([220.142.107.148]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CL8bg-0007rh-3i; Fri, 22 Oct 2004 19:14:10 -0400 Received: from 245.32.207.24 by web430.mail.yahoo.com; Sat, 23 Oct 2004 00:53:28 +0100 Message-ID: From: "Rebekah Tanner" To: dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org, enum-archive@ietf.org, enum-request@ietf.org Subject: Windows + Office only $80 Date: Sat, 23 Oct 2004 04:51:28 +0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--881904179403628" X-CS-IP: 64.216.157.201 X-Spam-Score: 13.0 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f ----881904179403628 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable











norm allegationmennonite rose aspherictrioxide holloway daytoncovalent meltdown dupontcyrus meteoric diphthongnothing leeward coachmaninsolent eastland blameworthyfreehold move dumpyinmate halma geesecast amaze facultyetruscan botulin seasideembarcadero elongate moldboardhandlebar carey huxleybetween antithetic cambridgebravery =20 ----881904179403628-- From dhcwg-bounces@ietf.org Fri Oct 22 20:38:46 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 UAA18114 for ; Fri, 22 Oct 2004 20:38:46 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLA8d-0001qA-S5 for dhcwg-web-archive@ietf.org; Fri, 22 Oct 2004 20:52:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL9rA-00028K-BL; Fri, 22 Oct 2004 20:34:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL9bc-0002Ig-T4 for dhcwg@megatron.ietf.org; Fri, 22 Oct 2004 20:18:01 -0400 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 UAA15952 for ; Fri, 22 Oct 2004 20:18:00 -0400 (EDT) Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL9oX-0001Ot-PV for dhcwg@ietf.org; Fri, 22 Oct 2004 20:31:22 -0400 Received: from [192.168.11.2] (206-169-64-120.vtc.net [206.169.64.120]) by toccata.fugue.com (Postfix) with ESMTP id C63851B2155; Fri, 22 Oct 2004 17:10:54 -0700 (MST) In-Reply-To: <004301c4b87f$dcc8efd0$6501a8c0@amer.cisco.com> References: <004301c4b87f$dcc8efd0$6501a8c0@amer.cisco.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Ted Lemon Subject: Re: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option Date: Fri, 22 Oct 2004 17:17:48 -0700 To: "Bernie Volz" X-Mailer: Apple Mail (2.619) X-Spam-Score: 0.0 (/) X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574 Content-Transfer-Encoding: 7bit Cc: dhcwg@ietf.org, "'Ralph Droms'" X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Content-Transfer-Encoding: 7bit Er, furthermore there's already a relay encapsulation method defined in the base DHCPv6 specification. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From vvzbmyixgsfm@portugalmail.pt Fri Oct 22 21:13:11 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 VAA19925; Fri, 22 Oct 2004 21:13:10 -0400 (EDT) Received: from cdm-24-250-169-11.bcst.cox-internet.com ([24.250.169.11]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CLAfs-0002P4-Ef; Fri, 22 Oct 2004 21:26:33 -0400 Received: from 176.150.248.23 by 65.174.115.32; Sat, 23 Oct 2004 02:06:30 +0100 Message-ID: From: "Leticia Benitez" Reply-To: "Leticia Benitez" To: dhcwg-request@ietf.org Subject: Windows XP Professional $50 Date: Sat, 23 Oct 2004 05:05:30 +0400 X-Mailer: AOL 8.0 for Windows US sub 343 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--65485715366531488693" X-Priority: 5 X-MSMail-Priority: Low X-IP: 55.245.168.240 X-Spam-Score: 16.3 (++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: d6b246023072368de71562c0ab503126 ----65485715366531488693 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable











nature yearndessicate bijection homereverie keyes sanchosinful list swimbackdrop riffle celeritybabbitt crosscut atwaterbehave rampage wiveaegis moan proscribecare unkempt faminecaretaker constrain continuantbrighten dromedary acquaintancefetter roadway sharecropscrape =20 ----65485715366531488693-- From dhcwg-bounces@ietf.org Fri Oct 22 23:18:19 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 XAA07219 for ; Fri, 22 Oct 2004 23:18:19 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLCd4-00049j-MS for dhcwg-web-archive@ietf.org; Fri, 22 Oct 2004 23:31:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLCIo-0004Cv-BL; Fri, 22 Oct 2004 23:10:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLCDw-0003Cq-EX for dhcwg@megatron.ietf.org; Fri, 22 Oct 2004 23:05:44 -0400 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 XAA06952 for ; Fri, 22 Oct 2004 23:05:43 -0400 (EDT) Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLCQs-00040z-Dq for dhcwg@ietf.org; Fri, 22 Oct 2004 23:19:07 -0400 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-2.cisco.com with ESMTP; 22 Oct 2004 20:13:24 -0700 Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i9N3586s016546; Fri, 22 Oct 2004 20:05:09 -0700 (PDT) Received: from volzw2k (che-vpn-cluster-2-248.cisco.com [10.86.242.248]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMM87094; Fri, 22 Oct 2004 23:05:07 -0400 (EDT) From: "Bernie Volz" To: "'Ted Lemon'" Subject: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option Date: Fri, 22 Oct 2004 23:05:07 -0400 Organization: Cisco Message-ID: <000601c4b8ad$1a343aa0$6501a8c0@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: quoted-printable Cc: dhcwg@ietf.org, "'Ralph Droms'" X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: quoted-printable Ted: Not sure what you're referring to. A relay would normally take a client message and place it into a = Relay-Forw with a Relay Message option containing the client's message. It can also = add any other options that it wants (and are allowed). In the base spec, = this might include an Interface-ID option, for example. And, why I suggested = was that this new I-D just define a "Radius Attribute" option which the = Relay Agent would add into the Relay-Forw message. - Bernie > -----Original Message----- > From: Ted Lemon [mailto:mellon@nominum.com]=20 > Sent: Friday, October 22, 2004 8:18 PM > To: Bernie Volz > Cc: dhcwg@ietf.org; 'Ralph Droms'; 'Wing Cheong Lau' > Subject: Re: [dhcwg] New draft on DHCPv6 Relay Information=20 > Option and RADIUS Attributes sub-option >=20 >=20 > Er, furthermore there's already a relay encapsulation method=20 > defined in=20 > the base DHCPv6 specification. >=20 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Sat Oct 23 01:19: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 BAA14103 for ; Sat, 23 Oct 2004 01:19:52 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLEWi-00065R-Op for dhcwg-web-archive@ietf.org; Sat, 23 Oct 2004 01:33:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLEA9-0004V8-Ry; Sat, 23 Oct 2004 01:09:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLE2w-0001P0-UV for dhcwg@megatron.ietf.org; Sat, 23 Oct 2004 01:02:31 -0400 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 BAA12896 for ; Sat, 23 Oct 2004 01:02:29 -0400 (EDT) Received: from toccata.fugue.com ([204.152.186.142]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLEFu-0005qN-Qe for dhcwg@ietf.org; Sat, 23 Oct 2004 01:15:55 -0400 Received: from [192.168.2.110] (206-169-64-119.vtc.net [206.169.64.119]) by toccata.fugue.com (Postfix) with ESMTP id 561DD1B26E9; Fri, 22 Oct 2004 21:55:24 -0700 (MST) In-Reply-To: <000601c4b8ad$1a343aa0$6501a8c0@amer.cisco.com> References: <000601c4b8ad$1a343aa0$6501a8c0@amer.cisco.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Ted Lemon Subject: Re: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option Date: Fri, 22 Oct 2004 22:02:20 -0700 To: "Bernie Volz" X-Mailer: Apple Mail (2.619) X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Cc: dhcwg@ietf.org, "'Ralph Droms'" X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit On Oct 22, 2004, at 8:05 PM, Bernie Volz wrote: > A relay would normally take a client message and place it into a > Relay-Forw > with a Relay Message option containing the client's message. It can > also add > any other options that it wants (and are allowed). In the base spec, > this > might include an Interface-ID option, for example. And, why I > suggested was > that this new I-D just define a "Radius Attribute" option which the > Relay > Agent would add into the Relay-Forw message. Right, that's what I was referring to. :') _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From gbvnwenabyu@sina.com.tw Sat Oct 23 06:50:36 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 GAA15740; Sat, 23 Oct 2004 06:50:36 -0400 (EDT) Received: from vdsl-130-13-113-169.phnx.qwest.net ([130.13.113.169]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CLJgr-0002mA-KA; Sat, 23 Oct 2004 07:04:07 -0400 Message-ID: <27483098850440.544rwb01039fw@hotmail.com> Received: from 10.251.231.148 by law5-xp98.law4.hotmail.com with DAV; Sat, 23 Oct 2004 10:46:34 -0100 Reply-To: "Tania Wolf" From: "Tania Wolf" To: Subject: legal operating systems for a fifth of the price Date: Sat, 23 Oct 2004 16:42:34 +0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--1672588898434986828" X-Spam-Score: 16.2 (++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 ----1672588898434986828 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable











dice infidelbujumbura advisable windbagredbud bistable sarcomacloddish inhalation peculatestanley balletomane buddhismconvocation aries chadwickpeppergrass acquiescent verselaughingstock sank badlandtrolley dynast daterhex contradistinguish dignityridicule trolley corvallisdc burrow clubdefendant =20 ----1672588898434986828-- From ydfpuvkc@directnet.com Sat Oct 23 07:50:51 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 HAA19794; Sat, 23 Oct 2004 07:50:51 -0400 (EDT) Received: from c-24-126-159-85.we.client2.attbi.com ([24.126.159.85]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CLKd7-0003oF-VL; Sat, 23 Oct 2004 08:04:20 -0400 Received: from 62.104.80.67 by 24.126.159.85; Sat, 23 Oct 2004 14:46:43 +0200 Message-ID: From: "Georgina Flynn" Reply-To: "Georgina Flynn" To: cfrg-request@ietf.org Subject: Virus Alert - september 17th Date: Sat, 23 Oct 2004 09:45:43 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--468748387233262458" X-Webmail-Time: Sat, 23 Oct 2004 09:45:43 -0300 X-Spam-Score: 10.9 (++++++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----468748387233262458 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




Remove=




leaden conversationbusboy andrew playgroundsyllabus eastern eyesightito maria chemistlarvae stagestruck bootleggingjocular demijohn orificeblandish credulous checkpointcubic barony configurationcrutch baleen tuffbrice norma packetoffspring cheese crueldurward instantaneous biracialfoolhardy mccarthy greenebikini colander chaffacid =20 ----468748387233262458-- From Victoria@wildmail.com Sat Oct 23 10:47:48 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 KAA00796; Sat, 23 Oct 2004 10:47:48 -0400 (EDT) Date: Sat, 23 Oct 2004 10:47:48 -0400 (EDT) From: Victoria@wildmail.com Received: from c-67-165-207-156.client.comcast.net ([67.165.207.156]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CLNOQ-0006hr-At; Sat, 23 Oct 2004 11:01:20 -0400 Received: from 72.88.154.64 by 67.165.207.156; Sat, 23 Oct 2004 10:39:38 -0500 Message-ID: From: "Elisabeth Godwin" To: dccp-admin@ietf.org, dccp-request@ietf.org, ddp-admin@ietf.org, dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dhksggnjkgshwvm@ietf.org Subject: Woww..8o-% 0ff Dccp-admin PID: 4 verna Date: Sat, 23 Oct 2004 20:54:05 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--50354819734473213339" Message-Id: X-Spam-Score: 3.2 (+++) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 ----50354819734473213339 Content-Type: text/plain; Content-Transfer-Encoding: 7Bit Buy Med's 0n-line! Up to 8o% off Vi-c0din, Cia|is, V|agra, Xanax, Vioxx, Valium and many more! Fast delivery! with wholesale prices! -No Con^sultation -No Prior Prescription Needed -Hu'ge Savings! See why our customers re-order more than any competitor! http://bestpills.mythingsusa.com/?k=S17h49 This is 1-time mai |ing. No rem0val are re qui-red vpr9Fd6wg5NPBASAYoelkrrZYOLp4tMNOhTfvVInu ----50354819734473213339-- From giegerich@cs.anu.edu.au Sat Oct 23 14:29:36 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 OAA13475 for ; Sat, 23 Oct 2004 14:29:36 -0400 (EDT) From: giegerich@cs.anu.edu.au Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLQr7-0001im-Gq for dhcwg-web-archive@ietf.org; Sat, 23 Oct 2004 14:43:10 -0400 Received: from adsl-64-168-134-154.dsl.snfc21.pacbell.net ([64.168.134.154] helo=localhost) by mx2.foretec.com with smtp (Exim 4.24) id 1CLQe3-0003zI-6j for dhcwg-web-archive@ietf.org; Sat, 23 Oct 2004 14:29:39 -0400 Date: Sun, 24 Oct 2004 05:37:16 +0000 Subject: Hello Dhcwg-web-archive Massive DlCK under Attack!! To: Dhcwg-web-archive References: <2D80BEAIH8G392HI@ietf.org> In-Reply-To: <2D80BEAIH8G392HI@ietf.org> Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; charset=Windows-1251; boundary="----=_NextPart_22348K4L62_L1477H0C9DE49J" X-Spam-Score: 13.7 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: a8a20a483a84f747e56475e290ee868e This is a multipart message in MIME format. ------=_NextPart_22348K4L62_L1477H0C9DE49J Content-Type: text/plain; charset=Windows-1251 Content-Transfer-Encoding: 8bit Massive DiIck in action! Real huge dics.... approx 15' and small little pussies.. hehe this looks very funny .. want see? http://www.coolandmore.com/gen_ads/gen_mail.php?grid=111&ape=gt2810 Fisting Virgin . Do you want see how hot virgins making fisting sex? one hand on pussy .. 2 hands,, i can understand.. but 4 hands? i think you should see it http://www.coolandmore.com/gen_ads/gen_mail.php?grid=272&ape=gt2810 www.coolandmore.com/takemeoff if you want stop it ------=_NextPart_22348K4L62_L1477H0C9DE49J Content-Type: text/html; charset=Windows-1251 Content-Transfer-Encoding: 8bit kdfkdjf kdj kd fkdjfkd

BlG DlCK IN ACTION!!

 

real huge dlcks!

approx 15'

and...small pussi3s

..yes..

 

CLlCK > WATCH > AND RELAX

www.coolandmore.com/takemeoff
if you want stop it
------=_NextPart_22348K4L62_L1477H0C9DE49J-- From ccgnfxqseicd@mindspring.com Sat Oct 23 16:33:09 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 QAA20862; Sat, 23 Oct 2004 16:33:09 -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 1CLSmV-0003e6-GM; Sat, 23 Oct 2004 16:46:44 -0400 Received: from user-12hdmn5.cable.mindspring.com ([69.22.218.229]) by mx2.foretec.com with smtp (Exim 4.24) id 1CLSZQ-0007Pg-3R; Sat, 23 Oct 2004 16:33:01 -0400 Received: from user-12hdmn5.cable.mindspring.com by mx12.mindspring.com with Microsoft SMTPSVC; Sat, 23 Oct 2004 14:33:14 -0600 Received: from 65.195.9.117 by user-12hdmn5.cable.mindspring.com with HTTP; Sat, 23 Oct 2004 14:32:20 -0600 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Luis Quinn" Reply-To: "Luis Quinn" Date: Sat, 23 Oct 2004 16:29:14 -0400 Message-ID: <33665759881597972-6108567@mindspring.com> Subject: Document Content-Type: text/plain; charset=windows-1251 To: Meza Dhcwg-web-archive X-Spam-Score: 7.2 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 7bit R e finance before Election when the r a tes will rise! It is your last chance http://www.aonmate.com/ You are already approv e d with 3.0 point Thank you. Luis Quinn ----------- agglomerate, tension at uruguay cecropia our us our mainline damnation the and our for a ax are cummins of to billy angeline enlargeable is gluey almost chart so of clot rodgers monmouth are not vitamin phenol Tpartridge burden bates westfield From axbwp@mensagem.cc Sat Oct 23 17:31:53 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 RAA23688; Sat, 23 Oct 2004 17:31:53 -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 1CLThZ-0004cw-41; Sat, 23 Oct 2004 17:45:29 -0400 Received: from [211.244.21.78] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CLTUP-0001ym-HG; Sat, 23 Oct 2004 17:31:54 -0400 Received: from %RECEIVED.music.com (%RECEIVED.music.com [3.240.24.0]) by 211.244.21.78 %REC_WITH; Sat, 23 Oct 2004 15:22:29 -0700 From: "Garry Davies" <%FROM_USER@music.com> Reply-To: "Garry Davies" <%FROM_USER@music.com> Subject: your eyebrows are like mine To: bmwg-admin@ietf.org, bmwg-archive@ietf.org, bmwg-request@ietf.org, cfrg@ietf.org, cfrg-admin@ietf.org, cfrg-request@ietf.org, chair@ietf.org, coya@ietf.org, dccp@ietf.org, dccp-admin@ietf.org, dccp-request@ietf.org, dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org Message-ID: <%MESSAGEID@music.com> X-Mailer: Microsoft Outlook Express 5.50.4522.1200 Date: Sun, 24 Oct 2004 01:22:29 +0300 Organization: Microsoft Outlook Express 5.50.4522.1200 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="75450651685263514" X-Spam-Score: 14.2 (++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a This is a multi-part message in MIME format. --75450651685263514 Content-Type: text/plain; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable %MAKE_TXT[3-6] --75450651685263514 Content-Type: text/html; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Article on the banned drug V10XX
READ HERE <= br>
urania neaterretrorocket uncle lancashiremerciful cenozoic longhandgodhead zest concertinaimputation poignant ammoniumdenunciate arclength sidewalksloven hereunder enospluck affectate jigsawdolomite credenza maximacharon --75450651685263514-- From swzsq@lycos.com Sat Oct 23 22:10:19 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 WAA08524; Sat, 23 Oct 2004 22:10:18 -0400 (EDT) Received: from daumesnil-7-82-227-123-91.fbx.proxad.net ([82.227.123.91]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CLY32-00008m-At; Sat, 23 Oct 2004 22:23:57 -0400 X-Message-Info: HAPPmPV6tGUwCv24Za6+EBMZc0oOQZU Received: from swghqcic69.cox.net ([38.248.130.139]) by bv96-g26.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Sun, 24 Oct 2004 07:08:12 +0500 Received: from Brianaj16x6gqq6f ([224.150.168.198]) by elwboizf11.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-7517199) with SMTP id <11631060707575.BSPS7545.ejnlkisi81.cox.net@inoperativev49r1sbj7q> for ; Sun, 24 Oct 2004 06:07:12 +0400 Message-ID: <502976p4q303$05140558$mg5r4389@Brianas20j8vtm7l> From: "Katelyn Whitehead" To: Subject: did you see her eyes Date: Sat, 23 Oct 2004 22:10:12 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--4979722114780488" X-Spam-Score: 9.3 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 ----4979722114780488 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




unsubscribe



cathode chrysanthemumceltic trichrome homeownavenue credible balzacmartinez soffit revertreble domineer athletenazi pinpoint waistcoatbateman jacksonville myersindecision parasympathetic blackbodyamericana burch wavefronthierarchic dealt curedeity downhill eduardomucosa arum chuteeliot =20 ----4979722114780488-- From markpassion@comcast.net Sun Oct 24 07:19:19 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 HAA19610; Sun, 24 Oct 2004 07:19:19 -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 1CLgcN-00041D-Qy; Sun, 24 Oct 2004 07:33:01 -0400 Received: from cm61-15-204-44.hkcable.com.hk ([61.15.204.44]) by mx2.foretec.com with smtp (Exim 4.24) id 1CLgP9-0001Fl-JY; Sun, 24 Oct 2004 07:19:20 -0400 Received: from wins86.comcast.net (wins86.comcast.net [50.72.224.0]) by 61.15.204.44 Microsoft SMTPSVC(5.0.2195.6824); Fri, 22 Oct 2004 19:19:40 -0800 Message-ID: <200410969823.q5S6gd58701772@comcast.net> X-Mailer: Microsoft Outlook Express 5.50.4920.2300 Date: Fri, 22 Oct 2004 19:19:40 -0800 From: "Pedro Dawson" Reply-To: "Pedro Dawson" To: diffserv-interest-admin@ietf.org Cc: directory-web-archive@ietf.org, dhcwg-admin@ietf.org, disman@ietf.org, dinaras@ietf.org, disman-request@ietf.org, dhcwg-request@ietf.org, diffserv-interest@ietf.org, dhcwg-web-archive@ietf.org, dhcwg@ietf.org, diffserv-interest-request@ietf.org, disman-admin@ietf.org Subject: check your lo an Status 65 Organization: Microsoft Outlook Express 5.50.4920.2300 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0900703116382691" X-Spam-Score: 17.6 (+++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b --0900703116382691 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit seapracticalnoisesfriendparttimer --0900703116382691 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7Bit Dèàr Hòmèòwnèr,
Interèst Ràtes àre àt thèir lowèst pòint in 40 yèars. Wè help yoù find thè bèst quòtè for yoùr situàtiòn by matching yoùr neèds with hùndreds òf lènders. Hòme Impròvemènt, Homè Eqùity, Loàns, and Morè. Evèn with lèss thàn perfèct crèdit. Jùst fill òut à qùick, simplè fòrm ànd jùmp-stàrt yòùr fùtùre plàns tòday.

Accèss òur Shòrt Fòrm

Moon Nail Ethnic High Instructor Interior Door Physical Television Sisters Justice Dish Tension Dance Happening Homeless Opera Dictionary Casual Middle Info Second Factory Entertainment Response Snow Count Target Lighter Made Code Restaurant Rival Bring Wet Bonus Fencing Decoration Chase Snow Appoint Coach Flooring Stop Dryer Bus News Dressing Technician Tool Calendar Lions Casting Personality Operator Stick Timetable Stay Limited Crystal Tie Appointment Cloudy Gods OK Wish Wonderful Stone Pound Stretch Appointment Soap Original Journalist Circle In Camp Sister Tough Scandalous Speak Garden National Frontier Mystery Break Beginning Unbalance Summary Something Royalty Classical Telephone Cover Fan Soft Rape Stick Days Lobby Figure Minor Gold Trend Hanger Exchange Lion Event Heavy Slow Trend Expert Enough Concert Lighter Claim --0900703116382691-- From Mcgrathmwg@zipee.com Sun Oct 24 21:30:09 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 VAA16350; Sun, 24 Oct 2004 21:30:09 -0400 (EDT) Received: from cpe-24-158-47-246.hky.nc.charter.com ([24.158.47.246]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CLttu-000174-Df; Sun, 24 Oct 2004 21:43:59 -0400 Received: from marriage.startfree.com ([128.96.144.99]) by 24.158.47.246 with ESMTP id <76057037239276.JQNI10041.lutz@paidforsurf.com> for ; Mon, 25 Oct 2004 00:23:05 -0100 Date: Mon, 25 Oct 2004 03:30:05 +0200 From: "Darlene Mckinney" Reply-To: "Darlene Mckinney" Message-Id: <510533r570l4005j74r1691t7t0545@pop> Organization: Microsoft CDO for Windows 2000 To: bmwg-archive@ietf.org Cc: bmwg-request@ietf.org, cfrg@ietf.org, cfrg-admin@ietf.org, cfrg-request@ietf.org, chair@ietf.org, coya@ietf.org, dccp@ietf.org, dccp-admin@ietf.org, dccp-request@ietf.org, dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org Subject: windows S0FTWARE half price! X-Mailer: Microsoft CDO for Windows 2000 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="1-910767960-8442527749=:87997" X-Spam-Score: 8.6 (++++++++) X-Spam-Flag: YES X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a --1-910767960-8442527749=:87997 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable --1-910767960-8442527749=:87997 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable UCLA Labs : system comparison

W1nd0ws X..P Pr0 + 0ff1ce X..P Pr0 - $80 (S@VE 420$ ) W1nd0ws X..P - $50 (S@VE 150$)

see complete results



pontific rapidperez width fluorocarbonbunyan champaign naturearbiter tyrosine exacerbatelakeside bayesian girlieassessor canker clandestinecutoff door hundredalexandria hackett clarendonbutler fivefold basetableland --1-910767960-8442527749=:87997-- From dhcwg-bounces@ietf.org Sun Oct 24 21:46:53 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 VAA17667 for ; Sun, 24 Oct 2004 21:46:52 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLu9x-0001OC-3P for dhcwg-web-archive@ietf.org; Sun, 24 Oct 2004 22:00:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLtuZ-0002Bn-6V; Sun, 24 Oct 2004 21:44:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLtsa-00021l-TP for dhcwg@megatron.ietf.org; Sun, 24 Oct 2004 21:42:36 -0400 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 VAA17360 for ; Sun, 24 Oct 2004 21:42:34 -0400 (EDT) Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLu5l-0001JB-S0 for dhcwg@ietf.org; Sun, 24 Oct 2004 21:56:24 -0400 Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I6400EHJA1SO9@mailout2.samsung.com> for dhcwg@ietf.org; Mon, 25 Oct 2004 10:41:52 +0900 (KST) Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I64007A59VY2N@mailout2.samsung.com> for dhcwg@ietf.org; Mon, 25 Oct 2004 10:38:22 +0900 (KST) Received: from LocalHost ([168.219.198.109]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0I64008ID9VY0V@mmp2.samsung.com> for dhcwg@ietf.org; Mon, 25 Oct 2004 10:38:22 +0900 (KST) Date: Mon, 25 Oct 2004 10:39:51 +0900 From: Soohong Daniel Park To: Dhcwg Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Content-type: multipart/mixed; boundary="Boundary_(ID_FMnrSZ3dLFZJVlopLaFKgA)" Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Subject: [dhcwg] FW: I-D ACTION:draft-madanapalli-dhcpv6-anycast-00.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a This is a multi-part message in MIME format. --Boundary_(ID_FMnrSZ3dLFZJVlopLaFKgA) Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7BIT FYI > Title : Anycast Address Assignment using DHCPv6 > Author(s) : S. Madanapalli, et al. > Filename : draft-madanapalli-dhcpv6-anycast-00.txt > Pages : 9 > Date : 2004-10-20 > > This document introduces a new option in DHCPv6 for Anycast/Shared > Unicast Address assignment for a particular type of service that > DHCPv6 Client provides. This address assignment is much similar to > other address types assignments, except that Anycast Address > assignment requires the specification of Service Type of the Anycast > or Shared Unicast Address. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-madanapalli-dhcpv6-anycast-00.txt Daniel (Soohong Daniel Park) Mobile Platform Lab. Samsung Electronics. --Boundary_(ID_FMnrSZ3dLFZJVlopLaFKgA) Content-type: Message/External-body; name=ATT00875.dat Content-disposition: attachment; filename=ATT00875.dat Content-Transfer-Encoding: 7bit Content-Type: text/plain Content-ID: <2004-10-21154132.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-madanapalli-dhcpv6-anycast-00.txt --Boundary_(ID_FMnrSZ3dLFZJVlopLaFKgA) Content-type: Message/External-body; name=draft-madanapalli-dhcpv6-anycast-00.txt Content-disposition: attachment; filename=draft-madanapalli-dhcpv6-anycast-00.txt Content-Transfer-Encoding: 7bit Content-Type: text/plain Content-ID: <2004-10-21154132.I-D@ietf.org> --Boundary_(ID_FMnrSZ3dLFZJVlopLaFKgA) Content-type: text/plain; name=ATT00878.txt Content-disposition: attachment; filename=ATT00878.txt Content-Transfer-Encoding: 7BIT _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --Boundary_(ID_FMnrSZ3dLFZJVlopLaFKgA) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --Boundary_(ID_FMnrSZ3dLFZJVlopLaFKgA)-- From Nelsonxfoi@nwnet.net Sun Oct 24 22:32:39 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 WAA20678; Sun, 24 Oct 2004 22:32:39 -0400 (EDT) Received: from d149-67-41-41.nap.wideopenwest.com ([67.149.41.41]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CLusP-0002AH-Cc; Sun, 24 Oct 2004 22:46:30 -0400 Received: from you.mkc.zaq.ne.jp ([24.124.33.154]) by 67.149.41.41 with ESMTP id <99979370452317.ZNGK64432.credenza@7119.net> for ; Sun, 24 Oct 2004 22:32:13 -0400 Date: Mon, 25 Oct 2004 04:32:13 +0200 From: "Tanisha Friedman" Reply-To: "Tanisha Friedman" Message-Id: <785702n496u0587n36g2195g8m8997@who've> Organization: Microsoft Outlook Express 6.00.2800.1158 To: dccp-request@ietf.org Cc: dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org, enum-archive@ietf.org, enum-request@ietf.org, iab@ietf.org, iesg@ietf.org, iesg-secretary@ietf.org, ietf@ietf.org, ietf-announce-request@ietf.org Subject: re:your sex problems X-Mailer: Microsoft Outlook Express 6.00.2800.1158 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="7-086555213-1072554870=:00815" X-Spam-Score: 12.1 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 --7-086555213-1072554870=:00815 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable




unsubscribe=




reducible spleenworti'd nigger militiapriori doldrum ginsenggenetic apple arousebacchus hummingbird elisabethternary pith droughtgrowl nurse she'llmuse embassy distributortoolmake decent christendomconsult --7-086555213-1072554870=:00815-- From Rollinsnwi@obsidiana.com.ar Mon Oct 25 06:26: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 GAA10740; Mon, 25 Oct 2004 06:26:29 -0400 (EDT) Received: from d53-64-73-173.nap.wideopenwest.com ([64.53.173.73]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CM2Gs-0002x4-Mk; Mon, 25 Oct 2004 06:40:25 -0400 Received: from 30.84.111.0 by 132.151.6.1; Mon, 25 Oct 2004 13:25:06 +0300 Message-ID: From: "Lori Walton" Reply-To: "Lori Walton" To: dccp@ietf.org Subject: help your girlfriend with her pain Date: Mon, 25 Oct 2004 07:22:06 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--8-303705318-9231863659=:06989" X-Priority: 5 X-CS-IP: 200.114.126.176 X-Spam-Score: 13.6 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a ----8-303705318-9231863659=:06989 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Stop Hurting!
VIC0D1N - Pain Relief !
0rder



enough



ginmill canberrasteiner citron humanburton carpathia vapidbookshelf asheville blousebehave chambermaid sketchyatheism spaniard calhounwest transmittable coincidentalumbra liberty persecutegrille synchronism comancheexogenous ----8-303705318-9231863659=:06989-- From Robertsvxkf@sportsline.com Mon Oct 25 07:15: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 HAA14341; Mon, 25 Oct 2004 07:15:38 -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 1CM32X-0003vC-5n; Mon, 25 Oct 2004 07:29:34 -0400 Received: from [218.19.77.206] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CM2p3-0004I6-Kx; Mon, 25 Oct 2004 07:15:34 -0400 Received: from chaotic.sites-internet.com ([147.76.168.68]) by 218.19.77.206 with ESMTP; Mon, 25 Oct 2004 05:13:42 -0600 Message-ID: <900759x808r8768k87m7820c5h2614@sites-internet.com> X-Mailer: The Bat! (v1.52f) Business Date: Mon, 25 Oct 2004 16:14:42 +0500 From: "Kasey Velazquez" Reply-To: "Kasey Velazquez" To: avt-request@ietf.org, bmwg@ietf.org, bmwg-admin@ietf.org, bmwg-archive@ietf.org, bmwg-request@ietf.org, cfrg@ietf.org, cfrg-admin@ietf.org, cfrg-request@ietf.org, chair@ietf.org, coya@ietf.org, dccp@ietf.org, dccp-admin@ietf.org, dccp-request@ietf.org, dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org Subject: Time magazine article on pain relief Organization: The Bat! (v1.52f) Business Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="9-784635337-1731016612=:85309" X-Spam-Score: 17.6 (+++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 --9-784635337-1731016612=:85309 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable --9-784635337-1731016612=:85309 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Pain Relief
VIC0D1N
More info



enough



wand coriolanusdarling rampage discriminatephonology bibb rockydigit broadway elongatekraft andersen fuselagelawyer schneider ferocityrascal dying cobbleamende didn't resultgenus cede negroidamanuensis --9-784635337-1731016612=:85309-- From djpqqxs@oct-net.ne.jp Mon Oct 25 10:56: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 KAA01906; Mon, 25 Oct 2004 10:56:01 -0400 (EDT) Received: from dhcp23185.oct-net.ne.jp ([202.220.185.185]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CM6Tt-0008Fj-10; Mon, 25 Oct 2004 11:09:59 -0400 Received: from dhcp23185.oct-net.ne.jp by vscan3.oct-net.ne.jp with HTTP; Mon, 25 Oct 2004 08:56:16 -0600 Received: from 139.204.39.128 by dhcp23185.oct-net.ne.jp with SMTP id 27006; Mon, 25 Oct 2004 08:55:46 -0600 Mime-Version: 1.0 Reply-To: "Robbie Doherty" Subject: and, besides him, a Date: Mon, 25 Oct 2004 07:49:16 -0700 Content-Type: text/plain; charset="WINDOWS-1257"; From: "Robbie Doherty" To: Milford Cclark Message-ID: <2280369027791-767755@oct-net.ne.jp> Content-Transfer-Encoding: 7bit X-Spam-Score: 1.1 (+) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Congratulations! You are a winner of our summer RA.TE. GIVE A WAY program. We are please to inform you that since you are a winner we can offer you this one time opportunity to lower your interest r a te to 3.99 percent. Your promotion code is 1158 Activate your code http://www.jklomnda.com/ Thank you. Robbie Doherty Promotion Department From mnvmyrrxpy@eresmas.com Mon Oct 25 12:15:12 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 MAA10502; Mon, 25 Oct 2004 12:15:10 -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 1CM7iK-0001wu-1s; Mon, 25 Oct 2004 12:29:09 -0400 Received: from 53528a13.cable.casema.nl ([83.82.138.19]) by mx2.foretec.com with smtp (Exim 4.24) id 1CM7Ur-0007cM-Cm; Mon, 25 Oct 2004 12:15:02 -0400 X-Message-Info: 14dqwQEiKLX874NExN659GPA66HJsdlFONtvGOPfnlPSogc92H Received: from juno.com (44.218.248.108) by q02-q2.juno.com with Microsoft SMTPSVC(1.9.5417.8105); Mon, 25 Oct 2004 23:26:42 +0500 Received: from juno.com (juno.com 32.92.0.188) by juno.com (8.12.10/8.12.9) with ESMTP id b60EOPQX507 for ; Mon, 25 Oct 2004 14:17:42 -0400 (EST) (envelope-from mnvmyrrxpy@eresmas.com) Received: from QSY796621924991 (modemcable5.8866-291.v.juno.com 16.192.184.41) (authenticated bits=3) by juno.com (8.12.10/8.12.9) with ESMTP id dkh34OW52yg086 for ; Mon, 25 Oct 2004 15:22:42 -0300 (EST) (envelope-from mnvmyrrxpy@eresmas.com) Message-ID: <68734xj2j7$ncy70ck39twy088$806i3gth800@EP98398380234278> From: "Kathryn Lawrence" To: Subject: Cljck here and get cheip prjces! This is the bast phemma site! sublimate Date: Mon, 25 Oct 2004 13:21:42 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--2180132384596066" X-Spam-Score: 8.3 (++++++++) X-Spam-Flag: YES X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 ----2180132384596066 Content-Type: text/html; Content-Transfer-Encoding: 7Bit Hi and welcome to our phhaemeci!
Bast Phaarmeci on the web! We appreciate the time you spend while looking for
new and better phhaemeci sites over the net, so we
decided to let you know about our site, our phhaemeci.
Come on now!

As you can see, we got large verjety of products. You are
more then welcomed to enter and view our site.


http://private.uahkld.biz/?wid=100183

nubia cola covenant blissful denebola. santo elusive beverage buchanan accessory scourge barbarous. rufus crania consign caribou mixup blowback. die foolish acrimonious bathe halide wingspan. apollonian cosmos velar schumann ascend shear intervene craft voluntary insignificant shrilly.
patrol confrere anhydrite horehound ogre. pittsburgh pulaski sixtieth analyst. yeshiva sophistry innate daniel dovekie calibrate chateaux coset steeplebush daddy. aleph colloquy reduce extremal cb peel ranch next. ----2180132384596066-- From dhcwg-bounces@ietf.org Mon Oct 25 13:03: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 NAA14300 for ; Mon, 25 Oct 2004 13:03:52 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM8Tg-0002zk-2L for dhcwg-web-archive@ietf.org; Mon, 25 Oct 2004 13:17:52 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM87d-0003cm-BT; Mon, 25 Oct 2004 12:55:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM83I-0002jy-7v for dhcwg@megatron.ietf.org; Mon, 25 Oct 2004 12:50:36 -0400 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 MAA13210 for ; Mon, 25 Oct 2004 12:50:32 -0400 (EDT) Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM8Gl-0002fw-Iz for dhcwg@ietf.org; Mon, 25 Oct 2004 13:04:32 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9PGnuRQ001914; Mon, 25 Oct 2004 09:49:56 -0700 (PDT) Received: from WLAU.qualcomm.com (wlau.qualcomm.com [129.46.74.167]) by neophyte.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9PGnr9A022319; Mon, 25 Oct 2004 09:49:53 -0700 (PDT) Message-Id: <6.0.0.22.2.20041025092643.040c8e10@qcmail1.qualcomm.com> X-Sender: wlau@qcmail1.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 25 Oct 2004 09:49:51 -0700 To: dhcwg@ietf.org From: Wing Cheong Lau Subject: Fwd: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option Mime-Version: 1.0 X-Spam-Score: 0.1 (/) X-Scan-Signature: b058151374d77ee76edaac850f7449fb Cc: volz@cisco.com, Ted.Lemon@nominum.com, rdroms@cisco.com X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1380722247==" Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 58b614506802734014829a093beb6879 --===============1380722247== Content-Type: multipart/alternative; boundary="=====================_127414882==.ALT" --=====================_127414882==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Dear Bernie and Ted, Thanks for your suggestion. My response is interlaced below. >X-BrightmailFiltered: true >From: "Bernie Volz" >To: "'Wing Cheong Lau'" , >Cc: "'Ralph Droms'" >Subject: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and >RADIUS Attributes sub-option >Date: Fri, 22 Oct 2004 17:41:17 -0400 >Organization: Cisco >X-Mailer: Microsoft Outlook, Build 10.0.6626 >Importance: Normal >X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.0.97340, Antispam-Data: >2004.10.22.1 >X-OriginalArrivalTime: 22 Oct 2004 21:42:20.0795 (UTC) >FILETIME=[025954B0:01C4B880] > >A very basic question ... why have a Relay Agent Information option and >have sub-options inside this? And, especially 8-bit suboptions. > >It seems to me that with the larger 16-bit DHCPv6 option space, we'd just >define an option to carry the "Radius Attributes" instead of placing this >under a general "Relay Agent" option. The context of the message is pretty >clear -- if it is from the relay, it can only be in a Relay-Forw (and >Relay-Reply) message option area. > >There's also another advantage to this. Take the DHCPv4 subnet-selection >option - there are two forms of this, one in for the relay agent and >another for the client. This won't be necessary in DHCPv6 as the LOCATION >of the message (either in the Client's Solicit, Request, ... or in a >Relay-Forw/Relay-Reply) tells us who added it and which we'd prefer to >use. This means only ONE option number is needed. > >So, I'd much rather see this specify a base option, >OPTION-RADIUS-ATTRIBUTES, and have this contain the Radius attributes in >the standard Radius encoding. So, it is just 16-bit option code, 16-bit >length, followed by the radius encoding (as 8-bit suboptions). > > >You can then specify that OPTION-RADIUS-ATTRIBUTES can only appear in the >Relay-Forw (and Relay-Reply) message and MUST NOT appear in client >messages themselves. > >- Bernie The original intent of specifying the sub-option was to try to simplify the definition of other sub-options in the future, e.g. the DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt and to save a byte of so if the relay needs to include multiple sub-options at the same time. On 2nd thought, this "uncommon case" may not worth the complexity. Your suggestion looks cleaner. Also, the use of 16-bit instead of 8-bit length field can eliminate the 255-byte length limit of RADIUS attributes to be included. I will make it a single-level option according your suggestion in the next revision. About the naming of the option, how about "OPTION-RELAYED-RADIUS-ATTRIBUTES" instead of "OPTION-RADIUS-ATTRIBUTES" ? This is to highlight the nature of this option, i.e. being inserted by the Relay Agent. Thanks again. Regards, Wing >-----Original Message----- >From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of >Wing Cheong Lau >Sent: Friday, October 22, 2004 12:45 PM >To: dhcwg@ietf.org >Subject: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS >Attributes sub-option > >Dear all, > >We have submitted a new draft on DHCPv6 Relay Information Option and >RADIUS Attributes sub-option last week. It's already available from the >ietf site > >http://www.ietf.org/internet-drafts/draft-droms-dhc-v6-relayopt-00.txt > >but I have not seen the official announcement so far. > >The draft basically carries over similar capabilities, namely, >RFC 3046 and draft-ietf-dhc-agentopt-radius-08.txt >from DHCPv4 to DHCPv6, with initial use cases targetting for >the 3GPP2 environment. > >Comments are welcome. > >Regards, > >Wing > >Abstract > > This document introduces the capabilities of the DHCPv4 Relay Agent > Information Option in RFC 3046 and the corresponding RADIUS- > Attributes Sub-option to DHCPv6. In particular, the document > describes a new DHCPv6 option called the Relay Agent Information > option which extends the set of DHCPv6 options as defined in RFC 3315 > and 3376. Following its DHCPv4 counterpart as defined in RFC 3046, > the new option is inserted by the DHCPv6 relay agent when forwarding > client-originated DHCPv6 packets to a DHCPv6 server. Servers > recognizing the Relay Agent Information option may use the > information to implement IP address or other parameter assignment > policies. The DHCP Server echoes the option back verbatim to the > relay agent in server-to-client replies, and the relay agent strips > the option before forwarding the reply to the client. The Relay Agent > Information option is organized as a single DHCPv6 option that > contains one or more "sub-options" that convey information known by > the relay agent. A RADIUS Attributes Sub-option, following its > DHCPv4 counterpart, is also defined. >Ted: > >Not sure what you're referring to. > >A relay would normally take a client message and place it into a Relay-Forw >with a Relay Message option containing the client's message. It can also add >any other options that it wants (and are allowed). In the base spec, this >might include an Interface-ID option, for example. And, why I suggested was >that this new I-D just define a "Radius Attribute" option which the Relay >Agent would add into the Relay-Forw message. >- Bernie > -----Original Message----- > From: Ted Lemon [mailto:mellon@nominum.com] > Sent: Friday, October 22, 2004 8:18 PM > To: Bernie Volz > Cc: dhcwg@ietf.org; 'Ralph Droms'; 'Wing Cheong Lau' > Subject: Re: [dhcwg] New draft on DHCPv6 Relay Information > Option and RADIUS Attributes sub-option > > > Er, furthermore there's already a relay encapsulation method > defined in > the base DHCPv6 specification. > --=====================_127414882==.ALT Content-Type: text/html; charset="us-ascii" Dear Bernie and Ted,

Thanks for your suggestion. My response is interlaced below.

X-BrightmailFiltered: true
From: "Bernie Volz" <volz@cisco.com>
To: "'Wing Cheong Lau'" <lau@qualcomm.com>, <dhcwg@ietf.org>
Cc: "'Ralph Droms'" <rdroms@cisco.com>
Subject: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option
Date: Fri, 22 Oct 2004 17:41:17 -0400
Organization: Cisco
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.0.97340, Antispam-Data: 2004.10.22.1
X-OriginalArrivalTime: 22 Oct 2004 21:42:20.0795 (UTC) FILETIME=[025954B0:01C4B880]

A very basic question ... why have a Relay Agent Information option and have sub-options inside this? And, especially 8-bit suboptions.
 
It seems to me that with the larger 16-bit DHCPv6 option space, we'd just define an option to carry the "Radius Attributes" instead of placing this under a general "Relay Agent" option. The context of the message is pretty clear -- if it is from the relay, it can only be in a Relay-Forw (and Relay-Reply) message option area.
 
There's also another advantage to this. Take the DHCPv4 subnet-selection option - there are two forms of this, one in for the relay agent and another for the client. This won't be necessary in DHCPv6 as the LOCATION of the message (either in the Client's Solicit, Request, ... or in a Relay-Forw/Relay-Reply) tells us who added it and which we'd prefer to use. This means only ONE option number is needed.
 
So, I'd much rather see this specify a base option, OPTION-RADIUS-ATTRIBUTES, and have this contain the Radius attributes in the standard Radius encoding. So, it is just 16-bit option code, 16-bit length, followed by the radius encoding (as 8-bit suboptions).

 
You can then specify that OPTION-RADIUS-ATTRIBUTES can only appear in the Relay-Forw (and Relay-Reply) message and MUST NOT appear in client messages themselves.
 
- Bernie

The original intent of specifying the sub-option was to try to simplify the definition of other sub-options in the future,
e.g. the DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt and to
save a byte of so if the relay needs to include multiple sub-options at the same time. 
On 2nd thought, this "uncommon case"  may not worth the complexity.

Your suggestion looks cleaner.
Also, the use of 16-bit instead of 8-bit length field can  eliminate the
255-byte length limit of RADIUS attributes to be included.
I will make it a single-level option according your suggestion in the next revision.


About the naming of the option, how about  "OPTION-RELAYED-RADIUS-ATTRIBUTES"
instead of "OPTION-RADIUS-ATTRIBUTES" ? This  is to highlight the nature of this option,
i.e.  being inserted by the Relay Agent.


Thanks again.

Regards,

Wing



-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Wing Cheong Lau
Sent: Friday, October 22, 2004 12:45 PM
To: dhcwg@ietf.org
Subject: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option

Dear all,

We have submitted a new draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option last week. It's already available from the ietf site

http://www.ietf.org/internet-drafts/draft-droms-dhc-v6-relayopt-00.txt

but I have not seen the official announcement so far.

The draft basically carries over similar capabilities, namely,
RFC 3046 and draft-ietf-dhc-agentopt-radius-08.txt
from DHCPv4 to DHCPv6, with initial use cases targetting for
the 3GPP2 environment.

Comments are welcome.

Regards,

Wing

Abstract
   
   This document introduces the capabilities of the DHCPv4 Relay Agent
   Information Option in RFC 3046 and the corresponding RADIUS-
   Attributes Sub-option to DHCPv6. In particular, the document
   describes a new DHCPv6 option called the Relay Agent Information
   option which extends the set of DHCPv6 options as defined in RFC 3315
   and 3376. Following its DHCPv4 counterpart as defined in RFC 3046,
   the new option is inserted by the DHCPv6 relay agent when forwarding
   client-originated DHCPv6 packets to a DHCPv6 server. Servers
   recognizing the Relay Agent Information option may use the
   information to implement IP address or other parameter assignment
   policies.  The DHCP Server echoes the option back verbatim to the
   relay agent in server-to-client replies, and the relay agent strips
   the option before forwarding the reply to the client. The Relay Agent
   Information option is organized as a single DHCPv6 option that
   contains one or more "sub-options" that convey information known by
   the relay agent.  A RADIUS Attributes Sub-option, following its
   DHCPv4 counterpart, is also defined. 

>Ted:
>
>Not sure what you're referring to.
>
>A relay would normally take a client message and place it into a Relay-Forw
>with a Relay Message option containing the client's message. It can also add
>any other options that it wants (and are allowed). In the base spec, this
>might include an Interface-ID option, for example. And, why I suggested was
>that this new I-D just define a "Radius Attribute" option which the Relay
>Agent would add into the Relay-Forw message.

>- Bernie

> -----Original Message-----
> From: Ted Lemon [mailto:mellon@nominum.com]
> Sent: Friday, October 22, 2004 8:18 PM
> To: Bernie Volz
> Cc: dhcwg@ietf.org; 'Ralph Droms'; 'Wing Cheong Lau'
> Subject: Re: [dhcwg] New draft on DHCPv6 Relay Information
> Option and RADIUS Attributes sub-option
>
>
> Er, furthermore there's already a relay encapsulation method
> defined in
> the base DHCPv6 specification.
>
--=====================_127414882==.ALT-- --===============1380722247== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --===============1380722247==-- From dhcwg-bounces@ietf.org Mon Oct 25 13:20:18 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 NAA15421 for ; Mon, 25 Oct 2004 13:20:18 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM8jZ-0003IP-W2 for dhcwg-web-archive@ietf.org; Mon, 25 Oct 2004 13:34:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM8Ra-0006cQ-LY; Mon, 25 Oct 2004 13:15:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM8O4-0005Wu-Vj for dhcwg@megatron.ietf.org; Mon, 25 Oct 2004 13:12:05 -0400 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 NAA14737 for ; Mon, 25 Oct 2004 13:12:01 -0400 (EDT) Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM8bY-00037Z-HP for dhcwg@ietf.org; Mon, 25 Oct 2004 13:26:01 -0400 Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 25 Oct 2004 13:11:33 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9PHBS7K024502; Mon, 25 Oct 2004 13:11:29 -0400 (EDT) Received: from volzw2k (che-vpn-cluster-2-248.cisco.com [10.86.242.248]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMN59909; Mon, 25 Oct 2004 13:11:27 -0400 (EDT) From: "Bernie Volz" To: "'Wing Cheong Lau'" , Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option Date: Mon, 25 Oct 2004 13:11:27 -0400 Organization: Cisco Message-ID: <003501c4bab5$aa200a90$6501a8c0@amer.cisco.com> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 In-Reply-To: <6.0.0.22.2.20041025092643.040c8e10@qcmail1.qualcomm.com> Importance: Normal X-Spam-Score: 0.1 (/) X-Scan-Signature: dae47ebd0d959deee2d6f67621ddb2e3 Cc: Ted.Lemon@nominum.com, rdroms@cisco.com X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1866488297==" Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 6ce9c9805f9fd7f2a8e6eb8268c6b0fc This is a multi-part message in MIME format. --===============1866488297== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0036_01C4BA94.230E6A90" This is a multi-part message in MIME format. ------=_NextPart_000_0036_01C4BA94.230E6A90 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Great, I have no objection to your suggested name other than it is = rather long - perhaps it will become known as OPTION_RRA. =20 Are you or Ralph going to discuss this at the upcoming DHC WG session = and request it become a WG work item? =20 =20 BTW, we don't need a DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt because the existing DHCPv6 = Vendor options can be used by the Relay Agent just fine. Again, it is WHERE = these options appear that indicates whether they are for the client (in the = client part of the message) or the relay, in the Relay-Forw or Relay-Reply part = of the message. That work is already done and is not needed!! =20 - Bernie =20 -----Original Message----- From: Wing Cheong Lau [mailto:lau@qualcomm.com]=20 Sent: Monday, October 25, 2004 12:50 PM To: dhcwg@ietf.org Cc: Ted.Lemon@nominum.com; rdroms@cisco.com; volz@cisco.com Subject: Fwd: RE: [dhcwg] New draft on DHCPv6 Relay Information Option = and RADIUS Attributes sub-option Dear Bernie and Ted, Thanks for your suggestion. My response is interlaced below. X-BrightmailFiltered: true From: "Bernie Volz" To: "'Wing Cheong Lau'" , Cc: "'Ralph Droms'" Subject: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and = RADIUS Attributes sub-option Date: Fri, 22 Oct 2004 17:41:17 -0400 Organization: Cisco X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.0.97340, Antispam-Data: 2004.10.22.1 X-OriginalArrivalTime: 22 Oct 2004 21:42:20.0795 (UTC) FILETIME=3D[025954B0:01C4B880] A very basic question ... why have a Relay Agent Information option and = have sub-options inside this? And, especially 8-bit suboptions. =20 It seems to me that with the larger 16-bit DHCPv6 option space, we'd = just define an option to carry the "Radius Attributes" instead of placing = this under a general "Relay Agent" option. The context of the message is = pretty clear -- if it is from the relay, it can only be in a Relay-Forw (and Relay-Reply) message option area. =20 There's also another advantage to this. Take the DHCPv4 subnet-selection option - there are two forms of this, one in for the relay agent and = another for the client. This won't be necessary in DHCPv6 as the LOCATION of the message (either in the Client's Solicit, Request, ... or in a Relay-Forw/Relay-Reply) tells us who added it and which we'd prefer to = use. This means only ONE option number is needed. =20 So, I'd much rather see this specify a base option, OPTION-RADIUS-ATTRIBUTES, and have this contain the Radius attributes in = the standard Radius encoding. So, it is just 16-bit option code, 16-bit = length, followed by the radius encoding (as 8-bit suboptions). =20 You can then specify that OPTION-RADIUS-ATTRIBUTES can only appear in = the Relay-Forw (and Relay-Reply) message and MUST NOT appear in client = messages themselves. =20 - Bernie The original intent of specifying the sub-option was to try to simplify = the definition of other sub-options in the future,=20 e.g. the DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt and to save a byte of so if the relay needs to include multiple sub-options at = the same time. =20 On 2nd thought, this "uncommon case" may not worth the complexity.=20 Your suggestion looks cleaner.=20 Also, the use of 16-bit instead of 8-bit length field can eliminate the 255-byte length limit of RADIUS attributes to be included. I will make it a single-level option according your suggestion in the = next revision. About the naming of the option, how about "OPTION-RELAYED-RADIUS-ATTRIBUTES" instead of "OPTION-RADIUS-ATTRIBUTES" ? This is to highlight the nature = of this option, i.e. being inserted by the Relay Agent. Thanks again. Regards, Wing -----Original Message----- From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf = Of Wing Cheong Lau Sent: Friday, October 22, 2004 12:45 PM To: dhcwg@ietf.org Subject: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option Dear all, We have submitted a new draft on DHCPv6 Relay Information Option and = RADIUS Attributes sub-option last week. It's already available from the ietf = site=20 http://www.ietf.org/internet-drafts/draft-droms-dhc-v6-relayopt-00.txt but I have not seen the official announcement so far. The draft basically carries over similar capabilities, namely,=20 RFC 3046 and draft-ietf-dhc-agentopt-radius-08.txt from DHCPv4 to DHCPv6, with initial use cases targetting for=20 the 3GPP2 environment. Comments are welcome. Regards, Wing Abstract=20 =20 This document introduces the capabilities of the DHCPv4 Relay Agent=20 Information Option in RFC 3046 and the corresponding RADIUS- Attributes Sub-option to DHCPv6. In particular, the document=20 describes a new DHCPv6 option called the Relay Agent Information=20 option which extends the set of DHCPv6 options as defined in RFC 3315 = and 3376. Following its DHCPv4 counterpart as defined in RFC 3046,=20 the new option is inserted by the DHCPv6 relay agent when forwarding=20 client-originated DHCPv6 packets to a DHCPv6 server. Servers=20 recognizing the Relay Agent Information option may use the=20 information to implement IP address or other parameter assignment=20 policies. The DHCP Server echoes the option back verbatim to the=20 relay agent in server-to-client replies, and the relay agent strips=20 the option before forwarding the reply to the client. The Relay Agent = Information option is organized as a single DHCPv6 option that=20 contains one or more "sub-options" that convey information known by=20 the relay agent. A RADIUS Attributes Sub-option, following its=20 DHCPv4 counterpart, is also defined. =20 >Ted: > >Not sure what you're referring to. > >A relay would normally take a client message and place it into a = Relay-Forw >with a Relay Message option containing the client's message. It can = also add >any other options that it wants (and are allowed). In the base spec, = this >might include an Interface-ID option, for example. And, why I suggested = was >that this new I-D just define a "Radius Attribute" option which the = Relay >Agent would add into the Relay-Forw message. >- Bernie > -----Original Message----- > From: Ted Lemon [mailto:mellon@nominum.com]=20 > Sent: Friday, October 22, 2004 8:18 PM > To: Bernie Volz > Cc: dhcwg@ietf.org; 'Ralph Droms'; 'Wing Cheong Lau' > Subject: Re: [dhcwg] New draft on DHCPv6 Relay Information=20 > Option and RADIUS Attributes sub-option >=20 >=20 > Er, furthermore there's already a relay encapsulation method=20 > defined in=20 > the base DHCPv6 specification. >=20 ------=_NextPart_000_0036_01C4BA94.230E6A90 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Great,=20 I have no objection to your suggested name other than it is rather = long -=20 perhaps it will become known as OPTION_RRA.
 
Are=20 you or Ralph going to discuss this at the upcoming DHC WG session and = request it=20 become a WG work item?
 
 
BTW,=20 we don't need a DHCPv6 version=20 of draft-ietf-dhc-vendor-suboption-00.txt because the existing DHCPv6 Vendor options can be used by the = Relay Agent=20 just fine. Again, it is WHERE these options appear that indicates = whether they=20 are for the client (in the client part of the message) or the relay, in = the=20 Relay-Forw or Relay-Reply part of the message. That work is already done = and is=20 not needed!!
 
-=20 Bernie
 
Dear Bernie and Ted,

Thanks for = your=20 suggestion. My response is interlaced below.

X-BrightmailFiltered: = true
From: "Bernie Volz" <volz@cisco.com>
To: "'Wing = Cheong=20 Lau'" <lau@qualcomm.com>, <dhcwg@ietf.org>
Cc: = "'Ralph=20 Droms'" <rdroms@cisco.com>
Subject: RE: [dhcwg] New draft = on DHCPv6=20 Relay Information Option and RADIUS Attributes sub-option
Date: = Fri, 22=20 Oct 2004 17:41:17 -0400
Organization: Cisco
X-Mailer: = Microsoft=20 Outlook, Build 10.0.6626
Importance: Normal
X-PMX-Version:=20 4.6.0.99824, Antispam-Core: 4.6.0.97340, Antispam-Data:=20 2004.10.22.1
X-OriginalArrivalTime: 22 Oct 2004 21:42:20.0795 = (UTC)=20 FILETIME=3D[025954B0:01C4B880]

A=20 very basic question ... why have a Relay Agent Information option = and have=20 sub-options inside this? And, especially 8-bit=20 suboptions.
 
It=20 seems to me that with the larger 16-bit DHCPv6 option space, we'd = just=20 define an option to carry the "Radius Attributes" instead of placing = this=20 under a general "Relay Agent" option. The context of the message is = pretty=20 clear -- if it is from the relay, it can only be in a Relay-Forw = (and=20 Relay-Reply) message option area.
 
There's also another advantage to this. = Take the DHCPv4=20 subnet-selection option - there are two forms of this, one in for = the relay=20 agent and another for the client. This won't be necessary in DHCPv6 = as the=20 LOCATION of the message (either in the Client's Solicit, Request, = ... or in=20 a Relay-Forw/Relay-Reply) tells us who added it and which we'd = prefer to=20 use. This means only ONE option number is = needed.
 
So, I'd much rather see this = specify a base=20 option, OPTION-RADIUS-ATTRIBUTES, and have this contain the Radius=20 attributes in the standard Radius encoding. So, it is just 16-bit = option=20 code, 16-bit length, followed by the radius encoding (as 8-bit=20 suboptions).

 
You can then specify that OPTION-RADIUS-ATTRIBUTES can only = appear in=20 the Relay-Forw (and Relay-Reply) message and MUST NOT appear in = client=20 messages themselves.
 
- Bernie

The original intent of specifying the sub-option = was to try=20 to simplify the definition of other sub-options in the future, =
e.g. the=20 DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt and = to
save a byte=20 of so if the relay needs to include multiple sub-options at the same=20 time. 
On 2nd thought, this "uncommon case"  may not = worth the=20 complexity.

Your suggestion looks cleaner.
Also, the use = of 16-bit=20 instead of 8-bit length field can  eliminate the
255-byte = length limit=20 of RADIUS attributes to be included.
I will make it a single-level = option=20 according your suggestion in the next revision.


About the = naming of=20 the option, how about  = "OPTION-RELAYED-RADIUS-ATTRIBUTES"
instead of=20 "OPTION-RADIUS-ATTRIBUTES" ? This  is to highlight the nature of = this=20 option,
i.e.  being inserted by the Relay = Agent.


Thanks=20 again.

Regards,

Wing



-----Original Message-----
From: Wing = Cheong Lau=20 [mailto:lau@qualcomm.com]
Sent: Monday, October 25, 2004 = 12:50=20 PM
To: dhcwg@ietf.org
Cc: Ted.Lemon@nominum.com;=20 rdroms@cisco.com; volz@cisco.com
Subject: Fwd: RE: [dhcwg] = New draft=20 on DHCPv6 Relay Information Option and RADIUS Attributes=20 sub-option

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of = Wing=20 Cheong Lau
Sent: Friday, October 22, 2004 12:45 PM
To: dhcwg@ietf.org
Subject: [dhcwg] New draft on DHCPv6 Relay Information = Option and=20 RADIUS Attributes sub-option

Dear all,

We have submitted a new draft on DHCPv6 Relay Information = Option and=20 RADIUS Attributes sub-option last week. It's already available = from the=20 ietf site

http://www.ietf.org/internet-drafts/draft-droms-dhc-v6= -relayopt-00.txt

but I have not seen the official announcement so far.

The draft basically carries over similar capabilities, namely, =
RFC 3046 and draft-ietf-dhc-agentopt-radius-08.txt
from DHCPv4 to DHCPv6, with initial use cases targetting for =
the 3GPP2 environment.

Comments are welcome.

Regards,

Wing

Abstract
   
   This document introduces the capabilities of the = DHCPv4=20 Relay Agent
   Information Option in RFC 3046 and the = corresponding=20 RADIUS-
   Attributes Sub-option to DHCPv6. In particular, = the=20 document
   describes a new DHCPv6 option called the Relay = Agent=20 Information
   option which extends the set of DHCPv6 options as = defined=20 in RFC 3315
   and 3376. Following its DHCPv4 counterpart as = defined in=20 RFC 3046,
   the new option is inserted by the DHCPv6 relay = agent when=20 forwarding
   client-originated DHCPv6 packets to a DHCPv6 = server.=20 Servers
   recognizing the Relay Agent Information option = may use=20 the
   information to implement IP address or other = parameter=20 assignment
   policies.  The DHCP Server echoes the option = back=20 verbatim to the
   relay agent in server-to-client replies, and the = relay=20 agent strips
   the option before forwarding the reply to the = client. The=20 Relay Agent
   Information option is organized as a single = DHCPv6 option=20 that
   contains one or more "sub-options" that convey=20 information known by
   the relay agent.  A RADIUS Attributes = Sub-option,=20 following its
   DHCPv4 counterpart, is also defined. =20

>Ted:
>
>Not sure what you're referring=20 to.
>
>A relay would normally take a client message and = place it=20 into a Relay-Forw
>with a Relay Message option containing the = client's=20 message. It can also add
>any other options that it wants (and = are=20 allowed). In the base spec, this
>might include an Interface-ID = option,=20 for example. And, why I suggested was
>that this new I-D just = define a=20 "Radius Attribute" option which the Relay
>Agent would add into = the=20 Relay-Forw message.

>- Bernie

> -----Original=20 Message-----
> From: Ted Lemon [mailto:mellon@nominum.com]
> Sent: = Friday, October=20 22, 2004 8:18 PM
> To: Bernie Volz
> Cc: dhcwg@ietf.org; = 'Ralph=20 Droms'; 'Wing Cheong Lau'
> Subject: Re: [dhcwg] New draft on = DHCPv6=20 Relay Information
> Option and RADIUS Attributes = sub-option
>=20
>
> Er, furthermore there's already a relay = encapsulation method=20
> defined in
> the base DHCPv6 specification.
>=20
------=_NextPart_000_0036_01C4BA94.230E6A90-- --===============1866488297== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --===============1866488297==-- From dhcwg-bounces@ietf.org Mon Oct 25 13:42: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 NAA17459 for ; Mon, 25 Oct 2004 13:42:52 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM95M-0003s1-JG for dhcwg-web-archive@ietf.org; Mon, 25 Oct 2004 13:56:51 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM8oP-0001km-2B; Mon, 25 Oct 2004 13:39:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM8kL-0001Sg-3x for dhcwg@megatron.ietf.org; Mon, 25 Oct 2004 13:35:06 -0400 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 NAA17001 for ; Mon, 25 Oct 2004 13:35:01 -0400 (EDT) Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM8xp-0003kH-AL for dhcwg@ietf.org; Mon, 25 Oct 2004 13:49:02 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9PHYURQ006237; Mon, 25 Oct 2004 10:34:31 -0700 (PDT) Received: from WLAU.qualcomm.com (wlau.qualcomm.com [129.46.74.167]) by neophyte.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9PHYR9A008113; Mon, 25 Oct 2004 10:34:28 -0700 (PDT) Message-Id: <6.0.0.22.2.20041025103245.040dbd80@qcmail1.qualcomm.com> X-Sender: wlau@qcmail1.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 25 Oct 2004 10:34:27 -0700 To: "Bernie Volz" , "'Wing Cheong Lau'" , From: Wing Cheong Lau Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option In-Reply-To: <003501c4bab5$aa200a90$6501a8c0@amer.cisco.com> References: <6.0.0.22.2.20041025092643.040c8e10@qcmail1.qualcomm.com> <003501c4bab5$aa200a90$6501a8c0@amer.cisco.com> Mime-Version: 1.0 X-Spam-Score: 0.1 (/) X-Scan-Signature: 8aa7cbc518894eb04182283f0682f662 Cc: Ted.Lemon@nominum.com, rdroms@cisco.com X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0842428322==" Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 8df1ceff7d5e1ba4a25ab9834397277b --===============0842428322== Content-Type: multipart/alternative; boundary="=====================_130089178==.ALT" --=====================_130089178==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed At 10:11 AM 10/25/2004, Bernie Volz wrote: >Great, I have no objection to your suggested name other than it is rather >long - perhaps it will become known as OPTION_RRA. > >Are you or Ralph going to discuss this at the upcoming DHC WG session and >request it become a WG work item? Yes, I have just requested for a 10-min slot and the objective is to request it to become a WG work-item. Regards, Wing > > >BTW, we don't need a DHCPv6 version of >draft-ietf-dhc-vendor-suboption-00.txt because the existing DHCPv6 Vendor >options can be used by the Relay Agent just fine. Again, it is WHERE these >options appear that indicates whether they are for the client (in the >client part of the message) or the relay, in the Relay-Forw or Relay-Reply >part of the message. That work is already done and is not needed!! > >- Bernie > >-----Original Message----- >From: Wing Cheong Lau [mailto:lau@qualcomm.com] >Sent: Monday, October 25, 2004 12:50 PM >To: dhcwg@ietf.org >Cc: Ted.Lemon@nominum.com; rdroms@cisco.com; volz@cisco.com >Subject: Fwd: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and >RADIUS Attributes sub-option > >Dear Bernie and Ted, > >Thanks for your suggestion. My response is interlaced below. > >>X-BrightmailFiltered: true >>From: "Bernie Volz" >>To: "'Wing Cheong Lau'" , >>Cc: "'Ralph Droms'" >>Subject: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and >>RADIUS Attributes sub-option >>Date: Fri, 22 Oct 2004 17:41:17 -0400 >>Organization: Cisco >>X-Mailer: Microsoft Outlook, Build 10.0.6626 >>Importance: Normal >>X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.0.97340, Antispam-Data: >>2004.10.22.1 >>X-OriginalArrivalTime: 22 Oct 2004 21:42:20.0795 (UTC) >>FILETIME=[025954B0:01C4B880] >> >>A very basic question ... why have a Relay Agent Information option and >>have sub-options inside this? And, especially 8-bit suboptions. >> >>It seems to me that with the larger 16-bit DHCPv6 option space, we'd just >>define an option to carry the "Radius Attributes" instead of placing this >>under a general "Relay Agent" option. The context of the message is >>pretty clear -- if it is from the relay, it can only be in a Relay-Forw >>(and Relay-Reply) message option area. >> >>There's also another advantage to this. Take the DHCPv4 subnet-selection >>option - there are two forms of this, one in for the relay agent and >>another for the client. This won't be necessary in DHCPv6 as the LOCATION >>of the message (either in the Client's Solicit, Request, ... or in a >>Relay-Forw/Relay-Reply) tells us who added it and which we'd prefer to >>use. This means only ONE option number is needed. >> >>So, I'd much rather see this specify a base option, >>OPTION-RADIUS-ATTRIBUTES, and have this contain the Radius attributes in >>the standard Radius encoding. So, it is just 16-bit option code, 16-bit >>length, followed by the radius encoding (as 8-bit suboptions). >> >> >>You can then specify that OPTION-RADIUS-ATTRIBUTES can only appear in the >>Relay-Forw (and Relay-Reply) message and MUST NOT appear in client >>messages themselves. >> >>- Bernie > >The original intent of specifying the sub-option was to try to simplify >the definition of other sub-options in the future, >e.g. the DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt and to >save a byte of so if the relay needs to include multiple sub-options at >the same time. >On 2nd thought, this "uncommon case" may not worth the complexity. > >Your suggestion looks cleaner. >Also, the use of 16-bit instead of 8-bit length field can eliminate the >255-byte length limit of RADIUS attributes to be included. >I will make it a single-level option according your suggestion in the next >revision. > > >About the naming of the option, how about "OPTION-RELAYED-RADIUS-ATTRIBUTES" >instead of "OPTION-RADIUS-ATTRIBUTES" ? This is to highlight the nature >of this option, >i.e. being inserted by the Relay Agent. > > >Thanks again. > >Regards, > >Wing > > > >>-----Original Message----- >>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of >>Wing Cheong Lau >>Sent: Friday, October 22, 2004 12:45 PM >>To: dhcwg@ietf.org >>Subject: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS >>Attributes sub-option >> >>Dear all, >>We have submitted a new draft on DHCPv6 Relay Information Option and >>RADIUS Attributes sub-option last week. It's already available from the >>ietf site >> >>http://www.ietf.org/internet-drafts/draft-droms-dhc-v6-relayopt-00.txt >>but I have not seen the official announcement so far. >>The draft basically carries over similar capabilities, namely, >>RFC 3046 and draft-ietf-dhc-agentopt-radius-08.txt >>from DHCPv4 to DHCPv6, with initial use cases targetting for >>the 3GPP2 environment. >>Comments are welcome. >>Regards, >>Wing >> >>Abstract >> >> This document introduces the capabilities of the DHCPv4 Relay Agent >> Information Option in RFC 3046 and the corresponding RADIUS- >> Attributes Sub-option to DHCPv6. In particular, the document >> describes a new DHCPv6 option called the Relay Agent Information >> option which extends the set of DHCPv6 options as defined in RFC 3315 >> and 3376. Following its DHCPv4 counterpart as defined in RFC 3046, >> the new option is inserted by the DHCPv6 relay agent when forwarding >> client-originated DHCPv6 packets to a DHCPv6 server. Servers >> recognizing the Relay Agent Information option may use the >> information to implement IP address or other parameter assignment >> policies. The DHCP Server echoes the option back verbatim to the >> relay agent in server-to-client replies, and the relay agent strips >> the option before forwarding the reply to the client. The Relay Agent >> Information option is organized as a single DHCPv6 option that >> contains one or more "sub-options" that convey information known by >> the relay agent. A RADIUS Attributes Sub-option, following its >> DHCPv4 counterpart, is also defined. > > >Ted: > > > >Not sure what you're referring to. > > > >A relay would normally take a client message and place it into a Relay-Forw > >with a Relay Message option containing the client's message. It can also add > >any other options that it wants (and are allowed). In the base spec, this > >might include an Interface-ID option, for example. And, why I suggested was > >that this new I-D just define a "Radius Attribute" option which the Relay > >Agent would add into the Relay-Forw message. > > >- Bernie > > > -----Original Message----- > > From: Ted Lemon [mailto:mellon@nominum.com] > > Sent: Friday, October 22, 2004 8:18 PM > > To: Bernie Volz > > Cc: dhcwg@ietf.org; 'Ralph Droms'; 'Wing Cheong Lau' > > Subject: Re: [dhcwg] New draft on DHCPv6 Relay Information > > Option and RADIUS Attributes sub-option > > > > > > Er, furthermore there's already a relay encapsulation method > > defined in > > the base DHCPv6 specification. > > --=====================_130089178==.ALT Content-Type: text/html; charset="us-ascii" At 10:11 AM 10/25/2004, Bernie Volz wrote:
Great, I have no objection to your suggested name other than it is rather long - perhaps it will become known as OPTION_RRA.
 
Are you or Ralph going to discuss this at the upcoming DHC WG session and request it become a WG work item?

Yes, I have just requested for a 10-min slot and the objective is to request it to become a WG work-item.

Regards,

Wing


 
 
BTW, we don't need a DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt because the existing DHCPv6 Vendor options can be used by the Relay Agent just fine. Again, it is WHERE these options appear that indicates whether they are for the client (in the client part of the message) or the relay, in the Relay-Forw or Relay-Reply part of the message. That work is already done and is not needed!!
 
- Bernie
 
-----Original Message-----
From: Wing Cheong Lau [mailto:lau@qualcomm.com]
Sent: Monday, October 25, 2004 12:50 PM
To: dhcwg@ietf.org
Cc: Ted.Lemon@nominum.com; rdroms@cisco.com; volz@cisco.com
Subject: Fwd: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option

Dear Bernie and Ted,

Thanks for your suggestion. My response is interlaced below.

X-BrightmailFiltered: true
From: "Bernie Volz" <volz@cisco.com>
To: "'Wing Cheong Lau'" <lau@qualcomm.com>, <dhcwg@ietf.org>
Cc: "'Ralph Droms'" <rdroms@cisco.com>
Subject: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option
Date: Fri, 22 Oct 2004 17:41:17 -0400
Organization: Cisco
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.0.97340, Antispam-Data: 2004.10.22.1
X-OriginalArrivalTime: 22 Oct 2004 21:42:20.0795 (UTC) FILETIME=[025954B0:01C4B880]

A very basic question ... why have a Relay Agent Information option and have sub-options inside this? And, especially 8-bit suboptions.
 
It seems to me that with the larger 16-bit DHCPv6 option space, we'd just define an option to carry the "Radius Attributes" instead of placing this under a general "Relay Agent" option. The context of the message is pretty clear -- if it is from the relay, it can only be in a Relay-Forw (and Relay-Reply) message option area.
 
There's also another advantage to this. Take the DHCPv4 subnet-selection option - there are two forms of this, one in for the relay agent and another for the client. This won't be necessary in DHCPv6 as the LOCATION of the message (either in the Client's Solicit, Request, ... or in a Relay-Forw/Relay-Reply) tells us who added it and which we'd prefer to use. This means only ONE option number is needed.
 
So, I'd much rather see this specify a base option, OPTION-RADIUS-ATTRIBUTES, and have this contain the Radius attributes in the standard Radius encoding. So, it is just 16-bit option code, 16-bit length, followed by the radius encoding (as 8-bit suboptions).

 
You can then specify that OPTION-RADIUS-ATTRIBUTES can only appear in the Relay-Forw (and Relay-Reply) message and MUST NOT appear in client messages themselves.
 
- Bernie

The original intent of specifying the sub-option was to try to simplify the definition of other sub-options in the future,
e.g. the DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt and to
save a byte of so if the relay needs to include multiple sub-options at the same time. 
On 2nd thought, this "uncommon case"  may not worth the complexity.

Your suggestion looks cleaner.
Also, the use of 16-bit instead of 8-bit length field can  eliminate the
255-byte length limit of RADIUS attributes to be included.
I will make it a single-level option according your suggestion in the next revision.


About the naming of the option, how about  "OPTION-RELAYED-RADIUS-ATTRIBUTES"
instead of "OPTION-RADIUS-ATTRIBUTES" ? This  is to highlight the nature of this option,
i.e.  being inserted by the Relay Agent.


Thanks again.

Regards,

Wing



-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Wing Cheong Lau
Sent: Friday, October 22, 2004 12:45 PM
To: dhcwg@ietf.org
Subject: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option

Dear all,
We have submitted a new draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option last week. It's already available from the ietf site

http://www.ietf.org/internet-drafts/draft-droms-dhc-v6-relayopt-00.txt
but I have not seen the official announcement so far.
The draft basically carries over similar capabilities, namely,
RFC 3046 and draft-ietf-dhc-agentopt-radius-08.txt
from DHCPv4 to DHCPv6, with initial use cases targetting for
the 3GPP2 environment.
Comments are welcome.
Regards,
Wing

Abstract
   
   This document introduces the capabilities of the DHCPv4 Relay Agent
   Information Option in RFC 3046 and the corresponding RADIUS-
   Attributes Sub-option to DHCPv6. In particular, the document
   describes a new DHCPv6 option called the Relay Agent Information
   option which extends the set of DHCPv6 options as defined in RFC 3315
   and 3376. Following its DHCPv4 counterpart as defined in RFC 3046,
   the new option is inserted by the DHCPv6 relay agent when forwarding
   client-originated DHCPv6 packets to a DHCPv6 server. Servers
   recognizing the Relay Agent Information option may use the
   information to implement IP address or other parameter assignment
   policies.  The DHCP Server echoes the option back verbatim to the
   relay agent in server-to-client replies, and the relay agent strips
   the option before forwarding the reply to the client. The Relay Agent
   Information option is organized as a single DHCPv6 option that
   contains one or more "sub-options" that convey information known by
   the relay agent.  A RADIUS Attributes Sub-option, following its
   DHCPv4 counterpart, is also defined. 

>Ted:
>
>Not sure what you're referring to.
>
>A relay would normally take a client message and place it into a Relay-Forw
>with a Relay Message option containing the client's message. It can also add
>any other options that it wants (and are allowed). In the base spec, this
>might include an Interface-ID option, for example. And, why I suggested was
>that this new I-D just define a "Radius Attribute" option which the Relay
>Agent would add into the Relay-Forw message.

>- Bernie

> -----Original Message-----
> From: Ted Lemon [mailto:mellon@nominum.com]
> Sent: Friday, October 22, 2004 8:18 PM
> To: Bernie Volz
> Cc: dhcwg@ietf.org; 'Ralph Droms'; 'Wing Cheong Lau'
> Subject: Re: [dhcwg] New draft on DHCPv6 Relay Information
> Option and RADIUS Attributes sub-option
>
>
> Er, furthermore there's already a relay encapsulation method
> defined in
> the base DHCPv6 specification.
>
--=====================_130089178==.ALT-- --===============0842428322== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --===============0842428322==-- From dhcwg-bounces@ietf.org Mon Oct 25 15:05:16 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 PAA24029 for ; Mon, 25 Oct 2004 15:05:16 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMAN9-0005Jg-PC for dhcwg-web-archive@ietf.org; Mon, 25 Oct 2004 15:19:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMA85-0003G4-1O; Mon, 25 Oct 2004 15:03:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMA5P-00014T-Iu for dhcwg@megatron.ietf.org; Mon, 25 Oct 2004 15:00:55 -0400 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 PAA23743 for ; Mon, 25 Oct 2004 15:00:53 -0400 (EDT) Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMAIt-0005FD-PL for dhcwg@ietf.org; Mon, 25 Oct 2004 15:14:53 -0400 Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9PIxEjH007569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 25 Oct 2004 11:59:15 -0700 (PDT) Received: from WLAU.qualcomm.com (wlau.qualcomm.com [129.46.74.167]) by crowley.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9PIxBba025838; Mon, 25 Oct 2004 11:59:12 -0700 (PDT) Message-Id: <6.0.0.22.2.20041025113534.040e29e0@qcmail1.qualcomm.com> X-Sender: wlau@qcmail1.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 25 Oct 2004 11:59:12 -0700 To: "Bernie Volz" , "'Wing Cheong Lau'" , From: Wing Cheong Lau Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option In-Reply-To: <003501c4bab5$aa200a90$6501a8c0@amer.cisco.com> References: <6.0.0.22.2.20041025092643.040c8e10@qcmail1.qualcomm.com> <003501c4bab5$aa200a90$6501a8c0@amer.cisco.com> Mime-Version: 1.0 X-Spam-Score: 0.1 (/) X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4 Cc: Ted.Lemon@nominum.com, rdroms@cisco.com X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1245802174==" Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 093efd19b5f651b2707595638f6c4003 --===============1245802174== Content-Type: multipart/alternative; boundary="=====================_135173158==.ALT" --=====================_135173158==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed At 10:11 AM 10/25/2004, Bernie Volz wrote: > >BTW, we don't need a DHCPv6 version of >draft-ietf-dhc-vendor-suboption-00.txt because the existing DHCPv6 Vendor >options can be used by the Relay Agent just fine. Again, it is WHERE these >options appear that indicates whether they are for the client (in the >client part of the message) or the relay, in the Relay-Forw or Relay-Reply >part of the message. That work is already done and is not needed!! > >- Bernie I see. However, the use of such vendor-options by the Relay Agent is kind of hidden/missing from the current text of RFC 3315. For example, Sections 22.16 and 22.17 of RFC 3315 only describe the use of such vendor options by the client and the server. The use of these options by the relay agent are not mentioned at all. While it is true that the table in Appendix A of RFC3315 does say the possible inclusion of the vendor options in the Relay-Forward/Relay-Reply message, the table in Appendix B seems to imply otherwise: In the table in Appendix B, while there are "*"'s for the Relay-Message and Interface ID rows under the Relay Forw./Relay Replay columns, no "*"'s are found for the Vendor Class/Vendor Info rows for the Relay Forw./Relay Replay columns. I think if Relay agent is allowed to include those vendor options in the Relay Forw/Replay messages, just like it includes the Interface option, the rows for the Vendor options should look like the row of the Interface option. Am I missing something ? or did I misunderstand the entire meaning of the table in Appendix B ? Actually, what does the "Option Field" column in the table mean ? Also what's the "Note" below the table refers to ? Would you share more clarification/ insights on this ? Thanks a lot in advance. Regards, Wing --=====================_135173158==.ALT Content-Type: text/html; charset="us-ascii" At 10:11 AM 10/25/2004, Bernie Volz wrote:

 
BTW, we don't need a DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt because the existing DHCPv6 Vendor options can be used by the Relay Agent just fine. Again, it is WHERE these options appear that indicates whether they are for the client (in the client part of the message) or the relay, in the Relay-Forw or Relay-Reply part of the message. That work is already done and is not needed!!
 
- Bernie


I see. However,  the use of such vendor-options by the Relay Agent is kind of hidden/missing from the current text of RFC 3315.
For example, Sections  22.16 and 22.17 of RFC 3315 only describe the use of such vendor options by the client and the server. The use of these options by the relay agent are not mentioned at all.

While it is true that the table in Appendix A of RFC3315
does say the possible inclusion of the vendor options in the Relay-Forward/Relay-Reply message, 
the table in Appendix B seems to imply otherwise:

In the table in Appendix B,  while there are  "*"'s  for the  Relay-Message and Interface ID rows under
the Relay Forw./Relay Replay columns,  no "*"'s are found  for the Vendor Class/Vendor Info rows for
the Relay Forw./Relay Replay columns. I think if Relay agent is allowed to include those vendor options in the
Relay Forw/Replay messages, just like it includes the Interface option, 
the rows for the  Vendor options should look like the row of  the Interface option.

Am I missing something ? or did I misunderstand the entire meaning of the table in Appendix B ?
Actually, what does the "Option Field" column in the table mean ?

Also what's the "Note" below the table refers to ?

Would you share more clarification/ insights on this ?

Thanks a lot in advance.

Regards,

Wing

--=====================_135173158==.ALT-- --===============1245802174== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --===============1245802174==-- From update882@suntrust.com Mon Oct 25 16:41:47 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 QAA06789; Mon, 25 Oct 2004 16:41:46 -0400 (EDT) Received: from c-24-19-39-245.client.comcast.net ([24.19.39.245]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMBsZ-0000Cp-GL; Mon, 25 Oct 2004 16:55:47 -0400 X-Message-Info: 7iledgtr5491RND_LC_CHAR[1-3]R/caAZJygvUjuBHwL06RDTtaa Received: from 85.128.107.128 by sy26-as811.swma536.yahoo.com with stumpage; Mon, 25 Oct 2004 23:52:41 +0200 Message-ID: <8520200517.48969@SunTrust Bank> Reply-To: "SunTrust Bank" From: "SunTrust Bank" To: "Disman-request" Subject: Urgent Message From SunTrust Date: Mon, 25 Oct 2004 15:50:41 -0600 MIME-Version: 1.0 (produced by paunchscurrilous 1.3) Content-Type: multipart/alternative; boundary="--2529472667283228972" X-Spam-Score: 8.9 (++++++++) X-Spam-Flag: YES X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 ----2529472667283228972 Content-Type: text/plain; charset="iso-6423-1" Content-Description: sire baud 3 Content-Transfer-Encoding: quoted-printable SunTrust Visa Check Card Protection Program In cooperation with other major American banks SunTrust has developed a new anti-fraud screening solution. This is an effort to prevent the recent surge in credit, debit card fraud and identity theft. The system is an advanced neural network that scrutinizes card transactions and ATM withdrawals to deliver a highly accurate risk score by analyzing the spending behavior of each cardholder along with the profile of each merchant and ATM. It will try to detect and stop any suspicious or fraudulent Visa Check Card activity. Register with our Visa Check Card Protection Program and you can use your card to shop online, in a store, or withdraw money at the ATM, and you'll be fully protected from unauthorized use of your card or account information. With SunTrust's Visa Check Card Protection Program Zero Liability policy, your liability for unauthorized transactions is $0-you pay nothing! All major American banks will implement this system within a near future. Note that this program only applies to your SunTrust Visa Check Card - which is linked directly to your checking account, not SunTrust credit cards. Please take a moment and follow the link below to securely register your card totally free of charge. http://200.114.234.181/verify/internetbanking.suntrust.com/index.php Regards, http://www.suntrust.com Security Department Do not reply to this e-mail as it is an unmonitored alias.=20 ----2529472667283228972-- From dhcwg-bounces@ietf.org Mon Oct 25 19:34:02 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 TAA16247 for ; Mon, 25 Oct 2004 19:34:02 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMEZI-0003bs-Ph for dhcwg-web-archive@ietf.org; Mon, 25 Oct 2004 19:48:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMBZD-0003fq-QX; Mon, 25 Oct 2004 16:35:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMBHr-0005cy-El for dhcwg@megatron.ietf.org; Mon, 25 Oct 2004 16:17:51 -0400 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 QAA02613 for ; Mon, 25 Oct 2004 16:17:48 -0400 (EDT) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMBVN-0007Fi-6e for dhcwg@ietf.org; Mon, 25 Oct 2004 16:31:49 -0400 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 25 Oct 2004 16:37:01 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9PKDtWT012255; Mon, 25 Oct 2004 16:13:56 -0400 (EDT) Received: from volzw2k (che-vpn-cluster-2-248.cisco.com [10.86.242.248]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMN78019; Mon, 25 Oct 2004 16:13:53 -0400 (EDT) From: "Bernie Volz" To: "'Wing Cheong Lau'" , Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option Date: Mon, 25 Oct 2004 16:13:52 -0400 Organization: Cisco Message-ID: <005b01c4bacf$266a6500$6501a8c0@amer.cisco.com> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 In-Reply-To: <6.0.0.22.2.20041025113534.040e29e0@qcmail1.qualcomm.com> Importance: Normal X-Spam-Score: 0.6 (/) X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba Cc: Ted.Lemon@nominum.com, rdroms@cisco.com X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1356082034==" Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3 This is a multi-part message in MIME format. --===============1356082034== Content-Type: multipart/alternative; boundary="----=_NextPart_000_005C_01C4BAAD.9F58C500" This is a multi-part message in MIME format. ------=_NextPart_000_005C_01C4BAAD.9F58C500 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable In a RFC 3315-bis, we'll need to correct this. Appendix B is in error = and should allow these options in the Relay-Forw/Relay-Reply. And, the description of the options should mention that these can also be used by = the relay agent <-> server communication. =20 But the intent was always there, as shown in Appendix A, to use these options for the relay agent as well. I think Appendix A is correct and complete (in terms of the options in the base specification.) =20 - Bernie =20 -----Original Message----- From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf = Of Wing Cheong Lau Sent: Monday, October 25, 2004 2:59 PM To: Bernie Volz; 'Wing Cheong Lau'; dhcwg@ietf.org Cc: Ted.Lemon@nominum.com; rdroms@cisco.com Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option = and RADIUS Attributes sub-option At 10:11 AM 10/25/2004, Bernie Volz wrote: BTW, we don't need a DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt because the existing DHCPv6 = Vendor options can be used by the Relay Agent just fine. Again, it is WHERE = these options appear that indicates whether they are for the client (in the = client part of the message) or the relay, in the Relay-Forw or Relay-Reply part = of the message. That work is already done and is not needed!! =20 - Bernie I see. However, the use of such vendor-options by the Relay Agent is = kind of hidden/missing from the current text of RFC 3315. For example, Sections 22.16 and 22.17 of RFC 3315 only describe the use = of such vendor options by the client and the server. The use of these = options by the relay agent are not mentioned at all.=20 While it is true that the table in Appendix A of RFC3315 does say the possible inclusion of the vendor options in the Relay-Forward/Relay-Reply message, =20 the table in Appendix B seems to imply otherwise:=20 In the table in Appendix B, while there are "*"'s for the = Relay-Message and Interface ID rows under the Relay Forw./Relay Replay columns, no "*"'s are found for the = Vendor Class/Vendor Info rows for the Relay Forw./Relay Replay columns. I think if Relay agent is allowed = to include those vendor options in the Relay Forw/Replay messages, just like it includes the Interface option, = the rows for the Vendor options should look like the row of the = Interface option. Am I missing something ? or did I misunderstand the entire meaning of = the table in Appendix B ? Actually, what does the "Option Field" column in the table mean ? Also what's the "Note" below the table refers to ? Would you share more clarification/ insights on this ? Thanks a lot in advance. Regards, Wing=20 ------=_NextPart_000_005C_01C4BAAD.9F58C500 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
In a=20 RFC 3315-bis, we'll need to correct this. Appendix B is in error and = should=20 allow these options in the Relay-Forw/Relay-Reply. And, the description = of the=20 options should mention that these can also be used by the = relay agent=20 <-> server communication.
 
But=20 the intent was always there, as shown in Appendix A, to use these = options for=20 the relay agent as well. I think Appendix A is correct and complete (in = terms of=20 the options in the base specification.)
 
-=20 Bernie
 
-----Original Message-----
From:=20 dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of = Wing Cheong Lau
Sent: Monday, October 25, 2004 2:59=20 PM
To: Bernie Volz; 'Wing Cheong Lau'; = dhcwg@ietf.org
Cc:=20 Ted.Lemon@nominum.com; rdroms@cisco.com
Subject: RE: RE: = [dhcwg] New=20 draft on DHCPv6 Relay Information Option and RADIUS Attributes=20 sub-option

At 10:11 AM 10/25/2004, Bernie Volz=20 wrote:


BTW, we don't need a DHCPv6 version of=20 draft-ietf-dhc-vendor-suboption-00.txt because the existing DHCPv6 Vendor options can be used by = the Relay=20 Agent just fine. Again, it is WHERE these options appear that = indicates=20 whether they are for the client (in the client part of the message) = or the=20 relay, in the Relay-Forw or Relay-Reply part of the message. That = work is=20 already done and is not needed!!
 
- Bernie


I = see.=20 However,  the use of such vendor-options by the Relay Agent is = kind of=20 hidden/missing from the current text of RFC 3315.
For example,=20 Sections  22.16 and 22.17 of RFC 3315 only describe the use of = such=20 vendor options by the client and the server. The use of these options = by the=20 relay agent are not mentioned at all.

While it is true that = the table=20 in Appendix A of RFC3315
does say the possible inclusion of the = vendor=20 options in the Relay-Forward/Relay-Reply message, 
the table = in=20 Appendix B seems to imply otherwise:

In the table in Appendix = B, =20 while there are  "*"'s  for the  Relay-Message and = Interface ID=20 rows under
the Relay Forw./Relay Replay columns,  no "*"'s are = found  for the Vendor Class/Vendor Info rows for
the Relay = Forw./Relay=20 Replay columns. I think if Relay agent is allowed to include those = vendor=20 options in the
Relay Forw/Replay messages, just like it includes = the=20 Interface option, 
the rows for the  Vendor options = should look=20 like the row of  the Interface option.

Am I missing = something ? or=20 did I misunderstand the entire meaning of the table in Appendix B=20 ?
Actually, what does the "Option Field" column in the table mean=20 ?

Also what's the "Note" below the table refers to = ?

Would you=20 share more clarification/ insights on this ?

Thanks a lot in=20 advance.

Regards,

Wing =

------=_NextPart_000_005C_01C4BAAD.9F58C500-- --===============1356082034== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --===============1356082034==-- From Duranwfofi@tiscali.co.uk Mon Oct 25 22:12:20 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 WAA01098; Mon, 25 Oct 2004 22:12:19 -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 1CMH2V-0007QA-0c; Mon, 25 Oct 2004 22:26:23 -0400 Received: from p4108-ipbf509marunouchi.tokyo.ocn.ne.jp ([61.214.29.108]) by mx2.foretec.com with smtp (Exim 4.24) id 1CMGoz-0000xQ-DB; Mon, 25 Oct 2004 22:12:26 -0400 X-Message-Info: mzrc4AFx867IkUZprXTDidjSVQpJ1 Received: from glued-dns.anet.net ([160.25.168.188]) by hif014-s23.anet.net with Microsoft SMTPSVC(5.0.2195.6824); Tue, 26 Oct 2004 00:05:35 -0200 Date: Tue, 26 Oct 2004 01:04:35 -0100 (CST) Message-Id: <68344736885781.GMG720pdzOd068745@ingrown860.partner88anet.net> To: dhcwg-admin@ietf.org Subject: are you guilty about your habits From: Barton Richard MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--9-577769707-9675041422=:66323" X-Spam-Score: 7.3 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d ----9-577769707-9675041422=:66323 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Wired Magazine s= pecial report:
Spyware is the leading cause of PC failure and hard drive corruption.
These malicious code and scripts compromise your privacy and lead to ident= ity theft.
Please scan= your computer


*r*e*l*e*a*s*e



distinguish sackalkali monologist idahoarrow transferring stewarddisney ammonium londonbypath t's lykessatanic ferret oxcarther humidistat dewittwesley additive countermensomersault atlantic swiftdiamond ----9-577769707-9675041422=:66323-- From Redmondhunrk@nas.com Mon Oct 25 22:35:48 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 WAA02543; Mon, 25 Oct 2004 22:35:48 -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 1CMHPE-0007pk-GS; Mon, 25 Oct 2004 22:49:52 -0400 Received: from [69.150.79.61] (helo=CLAY) by mx2.foretec.com with smtp (Exim 4.24) id 1CMHBf-0001lb-Ln; Mon, 25 Oct 2004 22:35:52 -0400 Received: from 133.248.72.211 by 69.150.79.61; Tue, 26 Oct 2004 06:34:39 +0400 Message-ID: From: "Dane Ford" Reply-To: "Dane Ford" To: dccp@ietf.org, dccp-admin@ietf.org, dccp-request@ietf.org, dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org Subject: important new urology article Date: Tue, 26 Oct 2004 03:29:39 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--2-239086930-8289716653=:39701" X-IP: 76.178.64.58 X-Spam-Score: 7.7 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----2-239086930-8289716653=:39701 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Is your Wife happy?
Vimax - Danish Orthopedic solutions
Article



s.= t.o.p




compose teammateredemptive fathom degeneratecarouse wrench cornfieldbaptismal disjunct traceconant incubate adayankton topcoat assaillocal cane rheumatismeliminate money agribusinessmonaco annihilate upgradehibachi =20 ----2-239086930-8289716653=:39701-- From Dalywdiz@netlords.de Mon Oct 25 23:47:31 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 XAA06976; Mon, 25 Oct 2004 23:47:31 -0400 (EDT) Received: from p6006-ipad32akatuka.ibaraki.ocn.ne.jp ([60.37.129.6]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMIWd-0000Vq-8L; Tue, 26 Oct 2004 00:01:36 -0400 X-Message-Info: 9hEXuj506iZD/viBazzZGwQLiaeaY8Ub Received: from ramo ([154.20.88.144]) by iuo29-mail.emittance.bootlegging.oneupmanship.cable.rogers.com (InterMail vM.5.01.05.12 413-892-368-947-053-91577305) with ESMTP id <50859188716921.CJRT840349.jpy36-mail.erudite.highroad.net.cable.rogers.com@birdwatch> for ; Tue, 26 Oct 2004 09:41:04 +0600 Message-ID: <768639e7ydlz$9463b6j9$9669t1d0@horsehair> Reply-To: "Lamont Giles" From: "Lamont Giles" To: Subject: Virus Alert - september 4th Date: Tue, 26 Oct 2004 07:38:04 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--9-648968720-0450994817=:72252" X-Spam-Score: 6.7 (++++++) X-Spam-Flag: YES X-Scan-Signature: 52e1467c2184c31006318542db5614d5 ----9-648968720-0450994817=:72252 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable scan your computer for malicious viruses and spyware


*r*e*l*e*a*s*e<= BR>


begonia naiveteelement indicter shipshapefeldspar switchman kingfisherragweed sorcery jeanniedon't emphases fjordabo carbuncle congresswomengrownup annum effectuatecelebes butane nosebagpracticable burdock cowslipcentigrade ----9-648968720-0450994817=:72252-- From cwokstmrgz@aafrica.com Tue Oct 26 05:14:08 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 FAA15211; Tue, 26 Oct 2004 05:14:08 -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 1CMNck-0006kT-Ip; Tue, 26 Oct 2004 05:28:16 -0400 Received: from roxanna-68.188.18.222.charter-stl.com ([68.188.18.222]) by mx2.foretec.com with smtp (Exim 4.24) id 1CMNP7-0003Ac-0F; Tue, 26 Oct 2004 05:14:09 -0400 Received: from dfivfamkfr.aaxis.com (rngzniqgrr.aaxis.com [30.76.200.12]) by 68.188.18.222 Microsoft SMTPSVC(6.0.3790.0); Tue, 26 Oct 2004 04:14:01 -0600 From: "Lucille Lindsay" Reply-To: "Lucille Lindsay" Subject: Your Mtg approval process # 475-411 To: iab@ietf.org Cc: mailman-admin@ietf.org, l2tpext-admin@ietf.org, calsch@ietf.org, ge-mib-admin@ietf.org, imrg-admin@ietf.org, workshop@ietf.org, dhcwg-web-archive@ietf.org, bdiffserv-interest@ietf.org, owner@ietf.org, cna-admin@ietf.org, diffserv@ietf.org Message-ID: X-Mailer: tglhROPP 2.6 Date: Tue, 26 Oct 2004 04:14:01 -0600 Organization: tglhROPP 2.6 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="8554353445452169383" X-Spam-Score: 7.3 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 This is a multi-part message in MIME format. --8554353445452169383 Content-Type: text/plain; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable JKDdZ --8554353445452169383 Content-Type: text/html; charset=%CHARSET Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Your mtg is in the process of being approved, for rates starting at 2= % Fixed.
Please use our secure site to fill-out your application
After doing so, you will be legible to recieve a 200-500K loan from one of= our lenders.

visit us at the Iink below:

Secure Web-Form

For nomore notices please visit: http://www.badcrednp4u.biz./blue/stop.htm= l

Thank You

476866 --8554353445452169383-- From CGHVZPDDDJKGHV@telus.net Tue Oct 26 07:36: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 HAA25994; Tue, 26 Oct 2004 07:36:36 -0400 (EDT) Message-Id: <200410261136.HAA25994@ietf.org> Received: from cable-65-88-94-121.grd.al.charter.com ([65.88.94.121]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMPqd-00010C-RF; Tue, 26 Oct 2004 07:50:44 -0400 Received: from aerobacter7wolfedebit (92.51.625.65) by mail7768.65.88.94.121 (gibedelaney ZA 2.6.901) id 81327M07KLK808ZE3934 for magma@ietf.org; Tue, 26 Oct 2004 06:40:24 -0500 X-MIME-Autoconverted: Yes Disclose-Recipients: No Discarded-X400-MTS-Extensions: Yes Alternate-Recipient: Allowed X-No-Archive: Yes Reply-To: "Sondra Barber" From: "Sondra Barber" To: magma@ietf.org Cc: secretariat@ietf.org, dhcwg-web-archive@ietf.org, nomcom@ietf.org, subip-area@ietf.org, sigtran@ietf.org, rpsec-admin@ietf.org Subject: Read: Important Information Date: Tue, 26 Oct 2004 05:36:24 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--581321947627661" X-Spam-Score: 5.0 (+++++) X-Spam-Flag: YES X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a ----581321947627661 Content-Type: text/html; charset="iso-6000-7" Content-Transfer-Encoding: 7Bit Hi,

Did you recieve my email from last week? I'm happy to tell you
that you are approved for a home loan with a 3.25% rate.

Your tracking number is # XN021
You must visit the link below in 24 hrs to confirm your details.

http://www.my-refi.net/j8/e7.php?v2l=63

Best Regards,
Sondra Barber
Manager
AFC Homes



Correspondence Options

----581321947627661-- From Elizabeth@awemail.com Tue Oct 26 08:36: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 IAA00759; Tue, 26 Oct 2004 08:36:58 -0400 (EDT) From: Elizabeth@awemail.com Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMQn3-00027n-FP; Tue, 26 Oct 2004 08:51:06 -0400 Received: from [219.241.176.222] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CMQZP-0000kD-BP; Tue, 26 Oct 2004 08:37:02 -0400 Received: from 123.159.186.172 by 219.241.176.222; Tue, 26 Oct 2004 16:35:14 +0300 Message-ID: ; Tue, 26 Oct 2004 11:18:45 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMTJg-000590-HB for dhcwg-web-archive@ietf.org; Tue, 26 Oct 2004 11:32:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMT4n-0007lv-BF; Tue, 26 Oct 2004 11:17:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMSwd-0006BQ-1I for dhcwg@megatron.ietf.org; Tue, 26 Oct 2004 11:09:07 -0400 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 LAA12434 for ; Tue, 26 Oct 2004 11:09:04 -0400 (EDT) Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMTAJ-0004v1-5I for dhcwg@ietf.org; Tue, 26 Oct 2004 11:23:15 -0400 Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i9QF8WF15592; Tue, 26 Oct 2004 11:08:32 -0400 (EDT) Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 26 Oct 2004 11:08:32 -0400 Message-ID: <591B780D9676844E8A704B5B013FFE92037E278A@zrc2hxm1.corp.nortel.com> From: "Kuntal Chowdhury" To: Bernie Volz , "'Wing Cheong Lau'" , dhcwg@ietf.org Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option andR ADIUS Attributes sub-option Date: Tue, 26 Oct 2004 11:08:16 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: a8a20a483a84f747e56475e290ee868e Cc: Ted.Lemon@nominum.com, rdroms@cisco.com X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f I have not followed this discussion yet, but I would like to notify the WG about the following draft we submitted: http://www.ietf.org/internet-drafts/draft-chowdhury-dhc-mip6-agentop-00.txt The idea is to allow the relay agent to convey some received information from RADIUS or DIAMETER server to the MN for MIP6 bootstrapping when the relay agent is also a NAS. " Abstract This document defines a new DHCPv6 option and number of sub-options for DHCP Relay Agent to facilitate Mobile IPv6 bootstrapping along with a AAA infrastructure. " Comments are welcome. Regards, Kuntal -----Original Message----- From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz Sent: Monday, October 25, 2004 3:14 PM To: 'Wing Cheong Lau'; dhcwg@ietf.org Cc: Ted.Lemon@nominum.com; rdroms@cisco.com Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option andRADIUS Attributes sub-option In a RFC 3315-bis, we'll need to correct this. Appendix B is in error and should allow these options in the Relay-Forw/Relay-Reply. And, the description of the options should mention that these can also be used by the relay agent <-> server communication. But the intent was always there, as shown in Appendix A, to use these options for the relay agent as well. I think Appendix A is correct and complete (in terms of the options in the base specification.) - Bernie -----Original Message----- From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Wing Cheong Lau Sent: Monday, October 25, 2004 2:59 PM To: Bernie Volz; 'Wing Cheong Lau'; dhcwg@ietf.org Cc: Ted.Lemon@nominum.com; rdroms@cisco.com Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option At 10:11 AM 10/25/2004, Bernie Volz wrote: BTW, we don't need a DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt because the existing DHCPv6 Vendor options can be used by the Relay Agent just fine. Again, it is WHERE these options appear that indicates whether they are for the client (in the client part of the message) or the relay, in the Relay-Forw or Relay-Reply part of the message. That work is already done and is not needed!! - Bernie I see. However, the use of such vendor-options by the Relay Agent is kind of hidden/missing from the current text of RFC 3315. For example, Sections 22.16 and 22.17 of RFC 3315 only describe the use of such vendor options by the client and the server. The use of these options by the relay agent are not mentioned at all. While it is true that the table in Appendix A of RFC3315 does say the possible inclusion of the vendor options in the Relay-Forward/Relay-Reply message, the table in Appendix B seems to imply otherwise: In the table in Appendix B, while there are "*"'s for the Relay-Message and Interface ID rows under the Relay Forw./Relay Replay columns, no "*"'s are found for the Vendor Class/Vendor Info rows for the Relay Forw./Relay Replay columns. I think if Relay agent is allowed to include those vendor options in the Relay Forw/Replay messages, just like it includes the Interface option, the rows for the Vendor options should look like the row of the Interface option. Am I missing something ? or did I misunderstand the entire meaning of the table in Appendix B ? Actually, what does the "Option Field" column in the table mean ? Also what's the "Note" below the table refers to ? Would you share more clarification/ insights on this ? Thanks a lot in advance. Regards, Wing _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From Fournieritfx@mycity.com.cn Tue Oct 26 12:20:24 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 MAA19723; Tue, 26 Oct 2004 12:20:09 -0400 (EDT) Received: from res-24-158-75-038.spa.sc.charter.com ([24.158.75.38]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMUH3-0006iP-Ov; Tue, 26 Oct 2004 12:34:20 -0400 Received: from ana.gt.rr.com ([20.136.188.54]) by 24.158.75.38 with ESMTP id <98327891315156.LOOK92067.boeotian@empirenet.com> for ; Tue, 26 Oct 2004 09:18:54 -0700 Date: Tue, 26 Oct 2004 18:19:54 +0200 From: "Aron Conner" Reply-To: "Aron Conner" Message-Id: <182665f705t5018b42y0528f1a7529@ripple> Organization: AOL 7.0 for Windows US sub 118 To: dhcwg-admin@ietf.org Cc: dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org, enum-archive@ietf.org, enum-request@ietf.org, iab@ietf.org, iesg@ietf.org, iesg-secretary@ietf.org, ietf@ietf.org, ietf-announce-request@ietf.org, ietf-info@ietf.org, ietf-registrar@ietf.org, ietf-request@ietf.org, ietf-secretariat@ietf.org, ietf-web@ietf.org, imrg@ietf.org Subject: Did you know 85% of world population is eligible? X-Mailer: AOL 7.0 for Windows US sub 118 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="1-867657810-5255278895=:97313" X-Spam-Score: 13.7 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 --1-867657810-5255278895=:97313 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable --1-867657810-5255278895=:97313 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable








<= BR>


foulmouth justinianrepeater coquette tornvermouth menlo thirtiethboson excusable accrualshare surgeon chalcociteincorrect christy bopchock camp churchwomanchairwomen airedale cushingbombast ryan combinejaguar --1-867657810-5255278895=:97313-- From Hartmanmybfn@inmind.com Tue Oct 26 12:21: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 MAA19940; Tue, 26 Oct 2004 12:21:00 -0400 (EDT) Received: from 200-55-116-214.dsl.prima.net.ar ([200.55.116.214]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMUHi-0006j4-IE; Tue, 26 Oct 2004 12:35:12 -0400 X-Message-Info: efb162SGqrfp63PAMqNniwnJBLfnXCmuoRCH0 Received: from aeneid-dns.wavecraft.com ([32.215.117.55]) by pe300-gtl29.wavecraft.com with Microsoft SMTPSVC(5.0.2195.6824); Tue, 26 Oct 2004 14:13:08 -0200 Date: Tue, 26 Oct 2004 19:11:08 +0300 (CST) Message-Id: <2767621.E189kdwKGNfi9226@armament82.sladang96wavecraft.com> To: dccp-request@ietf.org Subject: how you wish you were nineteen? From: Effie Davison MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--9-694571301-5592481060=:70089" X-Spam-Score: 12.7 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab ----9-694571301-5592481060=:70089 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable




unsubscribe




beaten cockpitaddress resemblant controlpreparative barton serieskeystone beard adroitaffluent debarring mckenzieresist intercalate seoulflue additional mossforbearance counterproposal bodleianembroil crux dewdropdrawn =20 ----9-694571301-5592481060=:70089-- From Hansenpfbh@postmaster.co.uk Tue Oct 26 15:23:24 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 PAA06364; Tue, 26 Oct 2004 15:23:23 -0400 (EDT) Received: from [81.8.188.197] (helo=JEPP-HYVCFQCUNU) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMX8Q-0002tx-Hs; Tue, 26 Oct 2004 15:37:36 -0400 Received: from diffractometer.gnshost.com ([32.252.2.68]) by 81.8.188.197 with ESMTP id <16618992633338.VWKR96577.commonweal@worldweb.net> for ; Tue, 26 Oct 2004 14:18:12 -0500 Date: Tue, 26 Oct 2004 21:23:12 +0200 From: "Alisha Sullivan" Reply-To: "Alisha Sullivan" Message-Id: <388442v972c3500c15i2597g8a2287@expurgate> Organization: Internet Mail Service (5.5.2650.21) To: bmwg-archive@ietf.org Subject: One time opportunity to live in the USA! X-Mailer: Internet Mail Service (5.5.2650.21) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="2-562937977-4364418040=:65418" X-Spam-Score: 12.1 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 93238566e09e6e262849b4f805833007 --2-562937977-4364418040=:65418 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable --2-562937977-4364418040=:65418 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable










titmouse cohoshtheodore tyrosine liquorantacid spurt tattletaleblouse slick forbesideal proximate wilhelmchug snuggle monolithdeterminate logarithm lockhartireland bloodbath orthantbrindle cordite delegatefestival =20 --2-562937977-4364418040=:65418-- From dhcwg-bounces@ietf.org Tue Oct 26 16:39: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 QAA15494 for ; Tue, 26 Oct 2004 16:39:05 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMYJi-0005ge-OQ for dhcwg-web-archive@ietf.org; Tue, 26 Oct 2004 16:53:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMXZn-0000vX-6Q; Tue, 26 Oct 2004 16:05:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMXTA-0005qx-BA; Tue, 26 Oct 2004 15:59:00 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09048; Tue, 26 Oct 2004 15:58:57 -0400 (EDT) Message-Id: <200410261958.PAA09048@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 26 Oct 2004 15:58:57 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-dhcpv6-opt-sntp-01.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : Simple Network Time Protocol Configuration Option for DHCPv6 Author(s) : A. Vijayabhaskar Filename : draft-ietf-dhc-dhcpv6-opt-sntp-01.txt Pages : 5 Date : 2004-10-26 This document describes a new DHCPv6 option for passing a list of Simple Network Time Protocol (SNTP) server addresses to a client. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-opt-sntp-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-dhcpv6-opt-sntp-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-dhcpv6-opt-sntp-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-26160459.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-dhcpv6-opt-sntp-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-dhcpv6-opt-sntp-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-26160459.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From Hookserzl@mn.rr.com Tue Oct 26 18:10:14 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 SAA06306; Tue, 26 Oct 2004 18:10:13 -0400 (EDT) Received: from [210.181.80.81] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMZju-0003lJ-7V; Tue, 26 Oct 2004 18:24:28 -0400 Received: from droop.infinitesimal.netlineuk.net (acceptant.antiquity.netlineuk.net [192.0.69.221]) by diffident.bacilli.netlineuk.net (5.82.7h1/6.82.5/j: discriminatory.cj,v 1.66 2511/93/72 06:16:08 utxjguf1 Exp $) with ESMTP id h6PM3uq91639 for ; Tue, 26 Oct 2004 19:07:19 -0400 GMT Received: from umvrzpni097.puddle.netlineuk.net (bsespcyh778.cheesecloth.netlineuk.net [226.148.180.136]) by no.em.netlineuk.net (6.46.5f9/3.08.4/f: dilatory.ct,v 1.66 9222/13/30 78:21:67 vdtcszc1 Exp $) with SMTP id h6CG5Km07800 for ; Wed, 27 Oct 2004 04:03:19 +0500 GMT From: HW_UO_LFs@netlineuk.net Received: from estuary.confucianism.gypsum.netlineuk.net ([128.231.83.176]) by tdmvzern309.pensive.netlineuk.net (HMBYY 2.5.2.11) with SMTP id M2581419776122937522 for ; Wed, 27 Oct 2004 04:06:19 +0500 Received: from appendage ([76.40.196.64) by ozark.russ.shorten.netlineuk.net with Microsoft SMTPSVC(5.0.5163.2084); Tue, 26 Oct 2004 18:06:19 -0500 To: Subject: MS Money 2004 $60 Date: Wed, 27 Oct 2004 02:09:19 +0300 Message-ID: <131n03a25vp6$f601f487$w6k2v6r8@indy.managua.netlineuk.net> MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: multipart/alternative; boundary="----=_NextPart_8-400149359-4811200146=:58843" X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 18.0 (++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 This is a multi-part message in MIME format. ------=_NextPart_8-400149359-4811200146=:58843 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -------------------------------------------------------------------------= ------- ------=_NextPart_8-400149359-4811200146=:58843 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIT Newsletter : system comparison

W1nd0ws X..P Pr0 + 0ff1ce X..P Pr0 - $80 (S@VE 420$ ) W1nd0ws X..P - $50 (S@VE 150$)

see complete results



%PHP johanson marthachard acerbity adamantpervert walsh accommodateaisle bedspread bellboylongstanding panther shouldcoleman elope daybreakcommune arcsine fragileconfirmatory crosslink guiltgalena alpha cunningfermion ------=_NextPart_8-400149359-4811200146=:58843-- From Edwardsgja@mol.net Tue Oct 26 18:44:13 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 SAA15756; Tue, 26 Oct 2004 18:44:12 -0400 (EDT) Date: Tue, 26 Oct 2004 18:44:12 -0400 (EDT) Received: from adsl-64-166-116-153.dsl.lsan03.pacbell.net ([64.166.116.153]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMaGn-0006ba-2r; Tue, 26 Oct 2004 18:58:28 -0400 X-Message-Info: 8eCYdJ52Ttqjki2wHfS5NM3xUhirxQ67 Received: from dns1daddy.com ([170.40.116.52]) by du3-y8.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Tue, 26 Oct 2004 21:38:20 -0100 Received: from hoycounty.com [127.0.0.1] by dns1breast.com (SMTPD32-7.12 ) id ZQ052184X3; Tue, 26 Oct 2004 15:36:20 -0700 Subject: good stomach synthesis From: Rochelle.Waters To: bmwg-archive@ietf.org Message-Id: <684307085614603.MO87698@socketproven.com> Content-Type: multipart/alternative; boundary="--0-966701056-6119353141=:16772" X-Spam-Score: 25.6 (+++++++++++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f ----0-966701056-6119353141=:16772 Content-Type: text/html; Content-Transfer-Encoding: 7Bit




unsubscribe




inconsistent orgyhopkins eater haberdasherycayuga abyssinia yourselfatlantica augur hermitecandy steak desideratagavel beplaster cairofeud budge corrigendumkaolinite carib plinysax archer brinesmythe ----0-966701056-6119353141=:16772-- From qjjxyecxiwy@ameritech.net Wed Oct 27 01:52:41 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 BAA07215; Wed, 27 Oct 2004 01:52:41 -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 1CMgxV-0005eY-MB; Wed, 27 Oct 2004 02:06:59 -0400 Received: from adsl-68-22-152-17.dsl.klmzmi.ameritech.net ([68.22.152.17]) by mx2.foretec.com with smtp (Exim 4.24) id 1CMgjd-0006ad-Sc; Wed, 27 Oct 2004 01:52:41 -0400 Received: from adsl-68-22-152-17.dsl.klmzmi.ameritech.net by aitmx4.prodigy.net with esmtp (Exim 3.33 #1) id 20827; Tue, 26 Oct 2004 23:52:58 -0600 Received: from 164.150.6.90 by adsl-68-22-152-17.dsl.klmzmi.ameritech.net with qdaovfl; Tue, 26 Oct 2004 23:51:53 -0600 Reply-To: "Roderick Z. Colbert" From: "Roderick Z. Colbert" To: Dhcwg-web-archive Mime-Version: 1.0 Subject: Re: Account Notification Date: Wed, 27 Oct 2004 03:50:58 -0200 Content-Transfer-Encoding: 7bit Message-ID: <12597115988736.64001.qmail@ameritech.net> Content-Type: text/plain; charset="iso-8859-4" X-Spam-Score: 6.0 (++++++) X-Spam-Flag: YES X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Congratulations! You are a winner of our summer RA.TE. GIVE A WAY program. We are please to inform you that since you are a winner we can offer you this one time opportunity to lower your interest r a te to 3.99 percent. Your promotion code is 1394 Activate your code http://www.aokmwenks.com/ Thank you. Roderick Z. Colbert Promotion Department From Kempjzsgw@lviv.ua Wed Oct 27 08:57:46 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 IAA01431; Wed, 27 Oct 2004 08:57:45 -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 1CMnan-0004jU-1F; Wed, 27 Oct 2004 09:12:07 -0400 Received: from rameau-1-81-57-199-163.fbx.proxad.net ([81.57.199.163]) by mx2.foretec.com with smtp (Exim 4.24) id 1CMnMq-0003E5-He; Wed, 27 Oct 2004 08:57:32 -0400 Received: from exacter778.lemel.fr ([115.213.218.70]) by doppler.lemel.fr (InterMail vK.4.74.37.57 086-963-323-59152883 license aebft3xd12618dy5060s45ci9653m8972) with SMTP id <86875577680385.WZVA96953.putnam@promethium767.lemel.fr> for ; Wed, 27 Oct 2004 18:52:33 +0600 Message-ID: <89817954016990.72442.shaven@hopeful571.lemel.fr> Received: from [219.94.184.82] by aircraft550.lemel.fr via HTTP; Wed, 27 Oct 2004 15:57:33 +0300 Date: Wed, 27 Oct 2004 17:52:33 +0500 (PDT) From: Randall Lamb Subject: is her daughter coping with the pain To: In-Reply-To: <174085r990a8$5n455yn2$9q160z3v@f8wqen0s3x2hd7> MIME-Version: 1.0 X-Mailer: The Bat! (v1.52f) Business Content-type: multipart/alternative; boundary="----=_NextPart_3-954880920-7883423833=:69824" X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 12.0 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 This is a multi-part message in MIME format. ------=_NextPart_3-954880920-7883423833=:69824 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -------------------------------------------------------------------------= ------- ------=_NextPart_3-954880920-7883423833=:69824 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable




Remove




koenig julepconfluent cryostat downtrendtheses candelabra buntparishioner torpedo lobstersydney euler ubiquitousghent sake ranierdoormen exegesis digestgloom conference czerniakjefferson wilfred slotbeirut ------=_NextPart_3-954880920-7883423833=:69824-- From dhcwg-bounces@ietf.org Wed Oct 27 09:10:12 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 JAA02124 for ; Wed, 27 Oct 2004 09:10:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMnmz-0004vV-FN for dhcwg-web-archive@ietf.org; Wed, 27 Oct 2004 09:24:34 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMnWq-0004XN-M6; Wed, 27 Oct 2004 09:07:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMnVP-0004Cv-6K for dhcwg@megatron.ietf.org; Wed, 27 Oct 2004 09:06:23 -0400 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 JAA01912 for ; Wed, 27 Oct 2004 09:06:21 -0400 (EDT) Received: from mxs2.siemens.at ([194.138.12.133]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMnjF-0004rt-Lk for dhcwg@ietf.org; Wed, 27 Oct 2004 09:20:43 -0400 Received: from vies1k7x.sie.siemens.at ([158.226.129.83]) by mxs2.siemens.at with ESMTP id i9RD5nun019467 for ; Wed, 27 Oct 2004 15:05:49 +0200 Received: from vies141a.sie.siemens.at (vies1kbx.sie.siemens.at [158.226.135.174]) by vies1k7x.sie.siemens.at (8.12.10/8.12.1) with ESMTP id i9RD5mmD008268 for ; Wed, 27 Oct 2004 15:05:48 +0200 Received: by vies141a.sie.siemens.at with Internet Mail Service (5.5.2653.19) id <4L37SHP2>; Wed, 27 Oct 2004 15:08:21 +0200 Message-ID: <4D50D5110555D5119F270800062B41650532AC4C@viee10pa.erd.siemens.at> From: Grubmair Peter To: "Dhcwg (E-mail)" Date: Wed, 27 Oct 2004 15:03:31 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Subject: [dhcwg] retransmission timeout in stateless DHCPv6 and preference option ? X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 If a statelesss dhcpv6 client receives a reply with preference option, it has to wait until retransmission timer expires to select reply highest preference. I wonder if client has to wait for timeout of retransmission timer if the first reply does not contain a preference option ? Or is the client allowed to use the info from the reply imediately ? best regards Peter _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From rpmun@bk.ru Wed Oct 27 09:57:48 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 JAA04620; Wed, 27 Oct 2004 09:57:48 -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 1CMoWt-0005hc-MB; Wed, 27 Oct 2004 10:12:10 -0400 Received: from [165.229.72.35] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CMoIu-0004un-Ta; Wed, 27 Oct 2004 09:57:33 -0400 X-Message-Info: 88+dwsakbz052/lFkoCBQgmqQVsfZH881Yp Received: (qmail 7112 invoked by uid 54423); Wed, 27 Oct 2004 19:49:18 +0500 Date: Wed, 27 Oct 2004 08:55:18 -0600 Message-ID: <83568740318741030145.06787206.rpmun@bk.ru> From: "Marilyn Huddleston" Reply-To: rpmun@bk.ru To: "Chair" MIME-Version: 1.0 (produced by eoceneconsanguineous 3.1) Content-Type: multipart/alternative; boundary="--0676470916924431005" X-Spam-Score: 7.5 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574 ----0676470916924431005 Content-Type: text/html; charset="iso-2[" ----0676470916924431005-- From Phillipsset@zaobao.com.sg Wed Oct 27 11:22:53 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 LAA14411; Wed, 27 Oct 2004 11:22:52 -0400 (EDT) Message-Id: <200410271522.LAA14411@ietf.org> Received: from dup-200-95-126-47.prod-infinitum.com.mx ([200.95.126.47]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMprP-0007vx-3u; Wed, 27 Oct 2004 11:37:16 -0400 Received: from hlelj8.oo.net ([131.48.167.28]) by swore.oo.net (InterMail vK.2.66.24.95 399-565-714-13329377 license vttap4hn8109gn9442f90oi6209j9705) with ESMTP id <21408565957050.OICL28196.amply@oo.net> for ; Wed, 27 Oct 2004 12:19:59 -0400 Received: from mail pickup service by oo.net with Microsoft SMTPSVC; Wed, 27 Oct 2004 19:22:59 +0300 Received: from 151.36.140.0 by zayihxldwc.oo.net with HTTP; Wed, 27 Oct 2004 13:19:59 -0300 (GMT) From: "Frankie Brewer" To: Subject: Fw: your mother needs to cope with the pain Date: Wed, 27 Oct 2004 20:21:59 +0400 MIME-Version: 1.0 X-Mailer: eGroups Message Poster Content-type: multipart/alternative; boundary="----=_NextPart_5-823594828-9080935599=:48053" X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 12.0 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da This is a multi-part message in MIME format. ------=_NextPart_5-823594828-9080935599=:48053 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -------------------------------------------------------------------------= ------- ------=_NextPart_5-823594828-9080935599=:48053 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable NO MIDDLEMEN=3DLOWER PR1CES
St0p pay1ng the 1nflated pharmacy pr1ces -
These gener1c meds are 1dent1cal t0 branded types!
ALL AT 1NCRED1BLE PR1CES!
Check 0ut 0ur c0mplete 1nv= ent0ry

NEW - V1COD1N
NEW - PHENTERM1NE

Gener1c V*1agra
Gener1c C*1al1s
Branded X*en1cal
Gener1c M*er1d1a
Gener1c P*r0pec1a
Gener1c G*luc0phage
Gener1c V*10xx
Gener1c C*elebrex
Gener1c P*ax1l
Gener1c Z*0l0ft
Gener1c L*1p1t0r

0RDER N0W
free sh1pp1ng 1n october


R*E*M**0V*E ME


prohibition hyacinthbladdernut bucharest daybedadipic respire bananachildhood nurture stellabathe crewman complaisantouch blonde piddlelegendre cycad snobbuteo ambuscade contraltoshoelace retention godfathermedicine ------=_NextPart_5-823594828-9080935599=:48053-- From Villanuevaxoapl@unicum.de Wed Oct 27 12:52:15 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 MAA21808; Wed, 27 Oct 2004 12:52:15 -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 1CMrFw-0001ZD-3K; Wed, 27 Oct 2004 13:06:41 -0400 Received: from c-24-98-251-139.atl.client2.attbi.com ([24.98.251.139]) by mx2.foretec.com with smtp (Exim 4.24) id 1CMr1u-0002JS-Jq; Wed, 27 Oct 2004 12:52:11 -0400 Received: from 236.220.152.16 by 65.246.255.50; Wed, 27 Oct 2004 10:46:00 -0600 Message-ID: From: "Cora Purvis" Reply-To: "Cora Purvis" To: cfrg-request@ietf.org, chair@ietf.org, coya@ietf.org, dccp@ietf.org, dccp-admin@ietf.org, dccp-request@ietf.org, dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org, enum-archive@ietf.org, enum-request@ietf.org Subject: stop paying full price for your S0FTWARE Date: Wed, 27 Oct 2004 19:42:00 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--1-371118030-0178777799=:08786" X-Priority: 5 X-CS-IP: 0.88.34.199 X-Spam-Score: 9.7 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 ----1-371118030-0178777799=:08786 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable PC magazine : system comparison

W1nd0ws X..P Pr0 + 0ff1ce X..P Pr0 - $80 (S@VE 420$ ) W1nd0ws X..P - $50 (S@VE 150$)

see complete results



siskin dalhousieincumbent compensable corbettalert bulrush scribehiss aggression helmsmansulfuric corpus inaccessibleaubrey porphyry fluorocarbonpropose celandine willowvalet phrasemake siftwhosoever alias dougbouncy=20 ----1-371118030-0178777799=:08786-- From Angelina_Hammock@alwaysbeconnected.com Wed Oct 27 13:38:11 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 NAA25608 for ; Wed, 27 Oct 2004 13:38:11 -0400 (EDT) Message-Id: <200410271738.NAA25608@ietf.org> Received: from 118.red-62-57-232.user.auna.net ([62.57.232.118]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMryJ-0002cJ-1g for dhcwg-web-archive@ietf.org; Wed, 27 Oct 2004 13:52:35 -0400 From: "Giovante Middaugh" To: dhcwg-web-archive@ietf.org Subject: Fwd: what is this? Date: Wed, 27 Oct 2004 17:36:56 -0100 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 7.2 (+++++++) X-Spam-Flag: YES X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: quoted-printable There appeared in the papers caricatures of every giganti= c and imaginary creature, from the white whale, the terrible "Moby Dick" o= f sub-arctic regions, to the immense kraken, whose tentacles could entangl= e a ship of five hundred tons and hurry it into the abyss of the ocean!!!=20=













discontinue Before eight days were over the Abraham Lincoln would be ploughing the wat= ers of the Pacific: Where, when, and how was it built? and how could its c= onstruction have been kept secret? Certainly a Government might possess su= ch a destructive machine? As public interest was in question, and transatl= antic communications suffered, their veracity could not be doubted.=20 From dhcwg-bounces@ietf.org Wed Oct 27 15:38:28 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 PAA06452 for ; Wed, 27 Oct 2004 15:38:28 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMtql-0005K8-8x for dhcwg-web-archive@ietf.org; Wed, 27 Oct 2004 15:52:54 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMtaA-0008OG-AR; Wed, 27 Oct 2004 15:35:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMtUE-0004PX-JM for dhcwg@megatron.ietf.org; Wed, 27 Oct 2004 15:29:34 -0400 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 PAA05579 for ; Wed, 27 Oct 2004 15:29:32 -0400 (EDT) Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMti9-00059K-K2 for dhcwg@ietf.org; Wed, 27 Oct 2004 15:43:58 -0400 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-2.cisco.com with ESMTP; 27 Oct 2004 12:38:09 -0700 Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i9RJSx6s013947 for ; Wed, 27 Oct 2004 12:28:59 -0700 (PDT) Received: from rdroms-w2k01.cisco.com ([161.44.65.190]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMP45981; Wed, 27 Oct 2004 15:28:58 -0400 (EDT) Message-Id: <4.3.2.7.2.20041027152418.022abf00@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 27 Oct 2004 15:28:56 -0400 To: From: Ralph Droms Subject: RE: [dhcwg] BCMCS server option drafts In-Reply-To: <002e01c4b7aa$3e045090$d0412ca1@amer.cisco.com> References: <4.3.2.7.2.20041021143445.02504d48@flask.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8 What about the deployment issue? The 3GGP2 specification will be ratified in November, with deployment following soon. Some service providers already have DHCP servers in place that must be updated for any new options. The options defined in the current drafts can likely be supported without code changes to existing servers, allowing for faster deployment. Use of a VIVSO sub-option would require code changes to existing servers. How long would it take to deploy DHCP server that can support VIVSO? BTW, we need more discussion of this issue *soon* due to the time constraints of the upcoming 3GPP2 standards process and deployment. - Ralph At 04:12 PM 10/21/2004 -0400, Bernie Volz wrote: >Personally, I'd like to see the DHCPv4 VIVSO get deployed and pushing these >options to using it would be a step at making this happen (as one would >expect 3GPP2 vendors to have some significant input to the decisions of DHCP >server vendors). > >It also means that 3GPP2 is free to define other VIVSO options in the future >within their own forum and need not go to the IETF (and DHC WG). I suspect >that this would provide much faster deployment for them in the future. > >Also, the DHCPv6 OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS are already >there for DHCPv6. > >BTW, 3GPP2 already has an enterprise-id number: > >5535 > 3rd Generation Partnership Project 2 (3GPP2) > Allen Long > along@cisco.com > >So, they'd be good to go! > >- Bernie > > > -----Original Message----- > > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] > > On Behalf Of Ralph Droms > > Sent: Thursday, October 21, 2004 2:35 PM > > To: dhcwg@ietf.org > > Subject: [dhcwg] BCMCS server option drafts > > > > > > We need to have a short WG conversation about two options > > that were discussed at the WG meeting in San Diego. The > > outcome of the conversation will be to determine consensus > > about taking on these two > > drafts: > > > > draft-chowdhury-dhc-bcmcv4-option-01.txt > > draft-chowdhury-dhc-bcmcv6-option-01.txt > > > > as dhc WG work items or recommending that 3GPP2 define > > vendor-identifying vendor-specific option (VIVSO; option code > > 125) sub-options to carry the information described in the drafts. > > > > If the WG consensus is to take on the drafts as WG work items > > drafts, are they acceptable as currently published? > > > > Because of the time constraints imposed by the 3GPP2 > > schedule, I'm going to cut off discussion on this topic next > > Thursday, 10/28, and determine WG consensus at that time. > > > > Here are some considerations for discussion: > > > > 3GPP2 has defined some vendor-specific sub-options, for > > example, to identify a MIP home agent for the DHCP client. > > > > A 3GPP2 client needs to specify to the DHCP server which > > parameters it needs - specifically, whether it needs to > > receive the BCMCS servers. If the current drafts are adopted, > > the client can simply use the parameter request list option > > (option code 55) for the request. If a VIVSO sub-option is > > used, 3GPP2 would also define a parameter request list sub-option. > > > > There is a deployment issue, as some service providers > > already have DHCP servers in place that must be updated for > > any new options. Is it the case that the options defined in > > the current drafts can be supported without code changes to > > existing servers? Use of a VIVSO sub-option would require > > code changes to existing servers. How long would it take to > > deploy DHCP server that can support VIVSO. > > > > BCMCS may be adopted across multiple technologies, so the > > options in the current drafts would not be specific to 3GPP2. > > However, the BCMCS specification has not adopted by other > > standards, yet, so we may need to define additional options > > for related services in the future if those services are not > > interoperable with the 3GPP2 BCMCS service. > > > > CableLabs has one option with sub-options (RFC 3495) rather > > than multiple options because: > > * wanted to avoid exhaustion of DHCP option code space; perhaps less > > of an issue with option code reclassification > > * would have used VIVSO if available > > * use of VIVSO with sub-options would give 3GPP2 freedom to define new > > sub-options on demand > > Do these considerations have an impact on our decision about > > how to proceed with the 3GPP2 options? > > > > - Ralph > > > > > > _______________________________________________ > > dhcwg mailing list > > dhcwg@ietf.org > > https://www1.ietf.org/mailman/listinfo/dhcwg > > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Wed Oct 27 16:52:46 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 QAA12880 for ; Wed, 27 Oct 2004 16:52:46 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMv0i-00078k-GS for dhcwg-web-archive@ietf.org; Wed, 27 Oct 2004 17:07:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMuaT-0005vT-JF; Wed, 27 Oct 2004 16:40:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMuUD-0003Sw-Ed for dhcwg@megatron.ietf.org; Wed, 27 Oct 2004 16:33:37 -0400 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 QAA10794 for ; Wed, 27 Oct 2004 16:33:35 -0400 (EDT) Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMui8-0006VI-4k for dhcwg@ietf.org; Wed, 27 Oct 2004 16:48:02 -0400 Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i9RKX0l29985; Wed, 27 Oct 2004 16:33:00 -0400 (EDT) Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Wed, 27 Oct 2004 16:32:59 -0400 Message-ID: <591B780D9676844E8A704B5B013FFE920382C07B@zrc2hxm1.corp.nortel.com> From: "Kuntal Chowdhury" To: Ralph Droms , volz@cisco.com Subject: RE: [dhcwg] BCMCS server option drafts Date: Wed, 27 Oct 2004 16:32:36 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1 I have a few questions on the possible use of DHCPv6 OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS to request vendor specific info: 1. Since the enterprise number is included in OPTION_VENDOR_OPTS, will it suffice to use only this option in the information request message from the DHCP client? Is the use of OPTION_VENDOR_CLASS mandatory while vendor specific options are requested? 2. Does the mere inclusion of OPTION_VENDOR_OPTS in the information request message indicate to the DHCP server that the DHCP client is requesting for some specific vendor specific options? 3. O-R-O has the format where each of requested option codes are listed in it. However, in OPTION_VENDOR_OPTS the encapsulated vendor-specific options field MUST be encoded as a sequence of code/length/value fields. What value does the DHCP client use while requesting for a vendor specific option? These things are not clearly defined in RFC3315. Regards, Kuntal >-----Original Message----- >From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] >On Behalf Of Ralph Droms >Sent: Wednesday, October 27, 2004 2:29 PM >To: dhcwg@ietf.org >Subject: RE: [dhcwg] BCMCS server option drafts > > > >What about the deployment issue? The 3GGP2 specification will >be ratified in November, with deployment following soon. Some >service providers already have DHCP servers in place that must >be updated for any new options. The options defined in the >current drafts can likely be supported without code changes to >existing servers, allowing for faster deployment. Use of a >VIVSO sub-option would require code changes to existing >servers. How long would it take to deploy DHCP server that >can support VIVSO? > >BTW, we need more discussion of this issue *soon* due to the >time constraints of the upcoming 3GPP2 standards process and >deployment. > >- Ralph > >At 04:12 PM 10/21/2004 -0400, Bernie Volz wrote: >>Personally, I'd like to see the DHCPv4 VIVSO get deployed and pushing >>these options to using it would be a step at making this >happen (as one >>would expect 3GPP2 vendors to have some significant input to the >>decisions of DHCP server vendors). >> >>It also means that 3GPP2 is free to define other VIVSO options in the >>future within their own forum and need not go to the IETF >(and DHC WG). >>I suspect that this would provide much faster deployment for them in >>the future. >> >>Also, the DHCPv6 OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS >are already >>there for DHCPv6. >> >>BTW, 3GPP2 already has an enterprise-id number: >> >>5535 >> 3rd Generation Partnership Project 2 (3GPP2) >> Allen Long >> along@cisco.com >> >>So, they'd be good to go! >> >>- Bernie >> >> > -----Original Message----- >> > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On >> > Behalf Of Ralph Droms >> > Sent: Thursday, October 21, 2004 2:35 PM >> > To: dhcwg@ietf.org >> > Subject: [dhcwg] BCMCS server option drafts >> > >> > >> > We need to have a short WG conversation about two options >that were >> > discussed at the WG meeting in San Diego. The outcome of the >> > conversation will be to determine consensus about taking on these >> > two >> > drafts: >> > >> > draft-chowdhury-dhc-bcmcv4-option-01.txt >> > draft-chowdhury-dhc-bcmcv6-option-01.txt >> > >> > as dhc WG work items or recommending that 3GPP2 define >> > vendor-identifying vendor-specific option (VIVSO; option code >> > 125) sub-options to carry the information described in the drafts. >> > >> > If the WG consensus is to take on the drafts as WG work items >> > drafts, are they acceptable as currently published? >> > >> > Because of the time constraints imposed by the 3GPP2 schedule, I'm >> > going to cut off discussion on this topic next Thursday, >10/28, and >> > determine WG consensus at that time. >> > >> > Here are some considerations for discussion: >> > >> > 3GPP2 has defined some vendor-specific sub-options, for >example, to >> > identify a MIP home agent for the DHCP client. >> > >> > A 3GPP2 client needs to specify to the DHCP server which >parameters >> > it needs - specifically, whether it needs to receive the BCMCS >> > servers. If the current drafts are adopted, the client can simply >> > use the parameter request list option (option code 55) for the >> > request. If a VIVSO sub-option is used, 3GPP2 would also define a >> > parameter request list sub-option. >> > >> > There is a deployment issue, as some service providers >already have >> > DHCP servers in place that must be updated for any new >options. Is >> > it the case that the options defined in the current drafts can be >> > supported without code changes to existing servers? Use >of a VIVSO >> > sub-option would require code changes to existing servers. > How long >> > would it take to deploy DHCP server that can support VIVSO. >> > >> > BCMCS may be adopted across multiple technologies, so the >options in >> > the current drafts would not be specific to 3GPP2. However, the >> > BCMCS specification has not adopted by other standards, yet, so we >> > may need to define additional options for related services in the >> > future if those services are not interoperable with the >3GPP2 BCMCS >> > service. >> > >> > CableLabs has one option with sub-options (RFC 3495) rather than >> > multiple options because: >> > * wanted to avoid exhaustion of DHCP option code space; >perhaps less >> > of an issue with option code reclassification >> > * would have used VIVSO if available >> > * use of VIVSO with sub-options would give 3GPP2 freedom >to define new >> > sub-options on demand >> > Do these considerations have an impact on our decision >about how to >> > proceed with the 3GPP2 options? >> > >> > - Ralph >> > >> > >> > _______________________________________________ >> > dhcwg mailing list >> > dhcwg@ietf.org >> > https://www1.ietf.org/mailman/listinfo/dhcwg >> > > > >_______________________________________________ >dhcwg mailing list >dhcwg@ietf.org >https://www1.ietf.org/mailman/listinfo/dhcwg > > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dqjltsgfkot@msn.com Wed Oct 27 21:03:09 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 VAA04532; Wed, 27 Oct 2004 21:03:09 -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 1CMyv3-0003wj-OO; Wed, 27 Oct 2004 21:17:38 -0400 Received: from pool-70-17-131-230.wma.east.verizon.net ([70.17.131.230]) by mx2.foretec.com with smtp (Exim 4.24) id 1CMyh2-0008EM-Ag; Wed, 27 Oct 2004 21:03:09 -0400 Received: from 204.90.76.58 by 70.17.131.230; Wed, 27 Oct 2004 19:04:15 -0700 Newsletter-ID: From: "Dion Manuel" Reply-To: "Dion Manuel" To: dhcwg-web-archive@ietf.org, dhksggnjkgshwvm@ietf.org, diffserv@ietf.org, diffserv-admin@ietf.org, diffserv-interest@ietf.org, diffserv-interest-admin@ietf.org, diffserv-interest-request@ietf.org, diffserv-request@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, disman@ietf.org, disman-admin@ietf.org Subject: Vi-c0din, Via-gra are Che.ap Here Dhcwg-web-archive Message-Id: Date: Wed, 27 Oct 2004 21:03:09 -0400 X-Spam-Score: 3.0 (+++) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 User ID: 7 transpond Date: Thu, 28 Oct 2004 05:05:15 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--4268822681331190567" ----4268822681331190567 Content-Type: text/plain; Content-Transfer-Encoding: 7Bit The L0west price of all med's is here. *Vic0din ($45 only) *Via-gra ($57 only) *Va|ium ($49 only) *Hydroc0done ($49 only) *Phen-termine ($88 only) We are the be-st available nowadays. http://bestpills.mythingsusa.com/?k=S17h49 This is 1- time mai-|ing. N0 re m0val are re qu|red OUnk5rljZwLqUzTCzWo0pwmAb6UByvwbKY0oXDVHQvz4teGMRY ----4268822681331190567-- From dhcwg-bounces@ietf.org Wed Oct 27 21:39: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 VAA07006 for ; Wed, 27 Oct 2004 21:39:27 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMzUC-0004Xt-Fv for dhcwg-web-archive@ietf.org; Wed, 27 Oct 2004 21:53:56 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMzF0-0008QN-IX; Wed, 27 Oct 2004 21:38:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMzEF-0008Kh-A4 for dhcwg@megatron.ietf.org; Wed, 27 Oct 2004 21:37:27 -0400 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 VAA06959 for ; Wed, 27 Oct 2004 21:37:25 -0400 (EDT) Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMzSA-0004W9-W6 for dhcwg@ietf.org; Wed, 27 Oct 2004 21:51:54 -0400 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-4.cisco.com with ESMTP; 27 Oct 2004 18:35:38 -0700 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i9S1Xm6s003472; Wed, 27 Oct 2004 18:33:49 -0700 (PDT) Received: from volzw2k (che-vpn-cluster-2-84.cisco.com [10.86.242.84]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMP72155; Wed, 27 Oct 2004 21:33:47 -0400 (EDT) From: "Bernie Volz" To: "'Kuntal Chowdhury'" , "'Ralph Droms'" Subject: RE: [dhcwg] BCMCS server option drafts Date: Wed, 27 Oct 2004 21:33:45 -0400 Organization: Cisco Message-ID: <000901c4bc8e$2a46d6c0$6401a8c0@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: <591B780D9676844E8A704B5B013FFE920382C07B@zrc2hxm1.corp.nortel.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 X-Spam-Score: 0.0 (/) X-Scan-Signature: 515708a075ffdf0a79d1c83b601e2afd Content-Transfer-Encoding: quoted-printable Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e178fd6cb61ffb6940cd878e7fea8606 Content-Transfer-Encoding: quoted-printable Hi: I believe the original model was for OPTION_VENDOR_CLASS to be similar = to DHCPv4 Vendor class identifier option (option 60) and for = OPTION_VENDOR_OPTS to be similar to DHCPv4 Vendor Specific Information (option 43). You might refer to draft-ietf-dhc-vendor-03.txt, while for DHCPv4, it = does have some additional information about how the options might be used. = That work is modeled on the DHCPv6 options. In particular, see section 4: 4. Vendor-Identifying Vendor-Specific Information Option DHCP clients and servers may use this option to exchange vendor- specific information. Either party may send this option, as needed. While a typical case might be for a client to send the Vendor-Identifying Vendor Class option, to elicit a useful Vendor-Identifying Vendor-Specific Information Option, there is no requirement for such a flow. It would be good to get general agreement on this as you're perhaps the first user. And, it would be best to set a "standard" for others to = follow. I kind of liked the DHCPv4 model, as it is much easier and clearly to understand (and implement for clients and servers): - A Client includes OPTION_VENDOR_CLASS to identify itself. - A Client MAY include OPTION_VENDOR_OPTS if it has vendor specific data (other than classing information) to communicate. - A Server includes OPTION_VENDOR_OPTS for matching enterprise IDs (and class data, if appropriate). This is only REQUIRED if the ORO includes = the OPTION_VENDOR_OPTS code (the ORO doesn't say which vendors; that is = handled by OPTION_VENDOR_CLASS). - I'm not sure why a server would ever need to include = OPTION_VENDOR_CLASS, though perhaps it could tell the client what implementation the server = is so that perhaps the client knows it could use some extended capabilities? = Or, the server could send back whatever the client sent to it? But, as draft-ietf-dhc-vendor-03.tx states, this is not the only = possible model. Note that in your case, I would assume that the OPTION_VENDOR_CLASS = would have your enterprise ID and some class information to indicate what capabilities the client supports (and therefore the server should = provide configuration for in the OPTION_VENDOR_OPTS). So, this is a good issue for the DHC WG to resolve and clarify for a = future RFC 3315bis. - Bernie > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20 > On Behalf Of Kuntal Chowdhury > Sent: Wednesday, October 27, 2004 4:33 PM > To: Ralph Droms; volz@cisco.com > Cc: dhcwg@ietf.org > Subject: RE: [dhcwg] BCMCS server option drafts >=20 >=20 > I have a few questions on the possible use of DHCPv6=20 > OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS to request vendor=20 > specific info: >=20 > 1. Since the enterprise number is included in=20 > OPTION_VENDOR_OPTS, will it suffice to use only this option=20 > in the information request message from the DHCP client? Is=20 > the use of OPTION_VENDOR_CLASS mandatory while vendor=20 > specific options are requested? >=20 > 2. Does the mere inclusion of OPTION_VENDOR_OPTS in the=20 > information request message indicate to the DHCP server that=20 > the DHCP client is requesting for some specific vendor=20 > specific options? > > 3. O-R-O has the format where each of requested option codes=20 > are listed in it. However, in OPTION_VENDOR_OPTS the=20 > encapsulated vendor-specific options field MUST be encoded as=20 > a sequence of code/length/value fields. What value does the=20 > DHCP client use while requesting for a vendor specific option?=20 >=20 > These things are not clearly defined in RFC3315. >=20 > Regards, > Kuntal >=20 > >-----Original Message----- > >From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] > >On Behalf Of Ralph Droms > >Sent: Wednesday, October 27, 2004 2:29 PM > >To: dhcwg@ietf.org > >Subject: RE: [dhcwg] BCMCS server option drafts > > > > > > > >What about the deployment issue? The 3GGP2 specification will > >be ratified in November, with deployment following soon. Some=20 > >service providers already have DHCP servers in place that must=20 > >be updated for any new options. The options defined in the=20 > >current drafts can likely be supported without code changes to=20 > >existing servers, allowing for faster deployment. Use of a=20 > >VIVSO sub-option would require code changes to existing=20 > >servers. How long would it take to deploy DHCP server that=20 > >can support VIVSO? > > > >BTW, we need more discussion of this issue *soon* due to the > >time constraints of the upcoming 3GPP2 standards process and=20 > >deployment. > > > >- Ralph > > > >At 04:12 PM 10/21/2004 -0400, Bernie Volz wrote: > >>Personally, I'd like to see the DHCPv4 VIVSO get deployed=20 > and pushing > >>these options to using it would be a step at making this=20 > >happen (as one > >>would expect 3GPP2 vendors to have some significant input to the > >>decisions of DHCP server vendors). > >> > >>It also means that 3GPP2 is free to define other VIVSO=20 > options in the > >>future within their own forum and need not go to the IETF=20 > >(and DHC WG). > >>I suspect that this would provide much faster deployment for them in > >>the future. > >> > >>Also, the DHCPv6 OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS > >are already > >>there for DHCPv6. > >> > >>BTW, 3GPP2 already has an enterprise-id number: > >> > >>5535 > >> 3rd Generation Partnership Project 2 (3GPP2) > >> Allen Long > >> along@cisco.com > >> > >>So, they'd be good to go! > >> > >>- Bernie > >> > >> > -----Original Message----- > >> > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On > >> > Behalf Of Ralph Droms > >> > Sent: Thursday, October 21, 2004 2:35 PM > >> > To: dhcwg@ietf.org > >> > Subject: [dhcwg] BCMCS server option drafts > >> > > >> > > >> > We need to have a short WG conversation about two options > >that were > >> > discussed at the WG meeting in San Diego. The outcome of the > >> > conversation will be to determine consensus about taking=20 > on these=20 > >> > two > >> > drafts: > >> > > >> > draft-chowdhury-dhc-bcmcv4-option-01.txt > >> > draft-chowdhury-dhc-bcmcv6-option-01.txt > >> > > >> > as dhc WG work items or recommending that 3GPP2 define > >> > vendor-identifying vendor-specific option (VIVSO; option code > >> > 125) sub-options to carry the information described in=20 > the drafts. > >> > > >> > If the WG consensus is to take on the drafts as WG work items > >> > drafts, are they acceptable as currently published? > >> > > >> > Because of the time constraints imposed by the 3GPP2=20 > schedule, I'm > >> > going to cut off discussion on this topic next Thursday,=20 > >10/28, and > >> > determine WG consensus at that time. > >> > > >> > Here are some considerations for discussion: > >> > > >> > 3GPP2 has defined some vendor-specific sub-options, for > >example, to > >> > identify a MIP home agent for the DHCP client. > >> > > >> > A 3GPP2 client needs to specify to the DHCP server which > >parameters > >> > it needs - specifically, whether it needs to receive the BCMCS > >> > servers. If the current drafts are adopted, the client=20 > can simply=20 > >> > use the parameter request list option (option code 55) for the=20 > >> > request. If a VIVSO sub-option is used, 3GPP2 would=20 > also define a=20 > >> > parameter request list sub-option. > >> > > >> > There is a deployment issue, as some service providers > >already have > >> > DHCP servers in place that must be updated for any new > >options. Is > >> > it the case that the options defined in the current drafts can be > >> > supported without code changes to existing servers? Use=20 > >of a VIVSO > >> > sub-option would require code changes to existing servers. > > How long > >> > would it take to deploy DHCP server that can support VIVSO. > >> > > >> > BCMCS may be adopted across multiple technologies, so the > >options in > >> > the current drafts would not be specific to 3GPP2. However, the > >> > BCMCS specification has not adopted by other standards,=20 > yet, so we=20 > >> > may need to define additional options for related=20 > services in the=20 > >> > future if those services are not interoperable with the=20 > >3GPP2 BCMCS > >> > service. > >> > > >> > CableLabs has one option with sub-options (RFC 3495) rather than > >> > multiple options because: > >> > * wanted to avoid exhaustion of DHCP option code space;=20 > >perhaps less > >> > of an issue with option code reclassification > >> > * would have used VIVSO if available > >> > * use of VIVSO with sub-options would give 3GPP2 freedom > >to define new > >> > sub-options on demand > >> > Do these considerations have an impact on our decision > >about how to > >> > proceed with the 3GPP2 options? > >> > > >> > - Ralph > >> > > >> > > >> > _______________________________________________ > >> > dhcwg mailing list > >> > dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg > >> > > > > > > >_______________________________________________ > >dhcwg mailing list > >dhcwg@ietf.org > >https://www1.ietf.org/mailman/listinfo/dhcwg > > > > >=20 > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg >=20 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From Mackecj@germanmail.com Thu Oct 28 03:09:03 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 DAA11994; Thu, 28 Oct 2004 03:09:03 -0400 (EDT) Received: from p2047-ipad29sizuokaden.shizuoka.ocn.ne.jp ([220.111.117.47] helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CN4d9-0001ed-Lp; Thu, 28 Oct 2004 03:23:34 -0400 Received: from hotmail.com ([176.68.219.62]) by bdeywou.milmail.com (Sun Java System Messaging Server 6.1 HotFix 0.02 (built Aug 19 2003)) with ESMTP id <3T8A9227GS13ITP8@bdeywou.milmail.com> for dhcwg@ietf.org (ORCPT dhcwg@ietf.org); Thu, 28 Oct 2004 00:06:21 -0700 (IST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 28 Oct 2004 05:01:21 -0200 Received: from 195.96.179.110 by by3xi.otb8.hotmail.msn.com with HTTP; Thu, 28 Oct 2004 10:04:21 +0300 (GMT) Date: Thu, 28 Oct 2004 04:59:21 -0200 From: Traci Becker Subject: Fw: is her brother coping with the pain X-Originating-IP: [82.80.252.164] X-Sender: Harmonpqqsr@hotmail.com To: dhcwg@ietf.org Message-id: MIME-version: 1.0 Content-type: text/html X-Originating-Email: [Harmonpqqsr@hotmail.com] Original-recipient: rfc757;dhcwg@ietf.org X-OriginalArrivalTime: Thu, 28 Oct 2004 02:01:21 -0500 (UTC) FILETIME=[28L682A0:12P9K6YN] X-Spam-Score: 13.8 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Are you in Pain?
VIC0D1N - A scientific breakthru !
0RDER N0W



enough



= clip coughactivism clever alimonyproblematic rembrandt basicphysiognomy dynamite childrenkilldeer farber morphologycaleb raffle lyonrevet duet amortchar alderman gettycounterman kitty concertvalve From dhcwg-bounces@ietf.org Thu Oct 28 03:14:56 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 DAA12527 for ; Thu, 28 Oct 2004 03:14:56 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN4it-0001mX-1w for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 03:29:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN4Ss-00008J-Mg; Thu, 28 Oct 2004 03:12:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CN4Rn-0008IR-NA for dhcwg@megatron.ietf.org; Thu, 28 Oct 2004 03:11:47 -0400 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 DAA12282 for ; Thu, 28 Oct 2004 03:11:46 -0400 (EDT) Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CN4fo-0001hj-9t for dhcwg@ietf.org; Thu, 28 Oct 2004 03:26:17 -0400 Received: from ocean.jinmei.org (shuttle.wide.toshiba.co.jp [3ffe:501:100f::35]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 4AD6B15210; Thu, 28 Oct 2004 16:11:37 +0900 (JST) Date: Thu, 28 Oct 2004 16:11:37 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Grubmair Peter Subject: Re: [dhcwg] retransmission timeout in stateless DHCPv6 and preference option ? In-Reply-To: <4D50D5110555D5119F270800062B41650532AC4C@viee10pa.erd.siemens.at> References: <4D50D5110555D5119F270800062B41650532AC4C@viee10pa.erd.siemens.at> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: "Dhcwg \(E-mail\)" X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 >>>>> On Wed, 27 Oct 2004 15:03:31 +0200, >>>>> Grubmair Peter said: > If a statelesss dhcpv6 client receives a reply with > preference option, it has to wait until retransmission > timer expires to select reply highest preference. Please let me check, which part of which RFC does specify this behavior? Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From Vickjlyfo@surfree.net.il Thu Oct 28 07:39: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 HAA02977; Thu, 28 Oct 2004 07:39:23 -0400 (EDT) Received: from ipn36372-f78710.cidr.lightship.net ([216.204.119.246]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CN8qo-00072Z-Dx; Thu, 28 Oct 2004 07:53:55 -0400 Received: from cockroach.swbell.net ([88.26.105.40]) by 216.204.119.246 with ESMTP; Thu, 28 Oct 2004 15:36:00 +0400 Message-ID: <029361f824d1778o35q4299o1z4310@swbell.net> X-Mailer: eGroups Message Poster Date: Thu, 28 Oct 2004 06:39:00 -0500 From: "Lisa Stone" Reply-To: "Lisa Stone" To: cfrg-request@ietf.org Subject: Norton virus warning - september 3rd Organization: eGroups Message Poster Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="1-627142907-9120026257=:58580" X-Spam-Score: 9.5 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 --1-627142907-9120026257=:58580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable --1-627142907-9120026257=:58580 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Is your PC infecte= d ?
Viruses are the leading cause of PC failure and hard drive corruption.
= Please scan = your computer


*r*e*l*e*a*s*e<= /A>



gallantry crumblecolatitude prospectus inspirationprissy aldermen cathodicteletypewrite kramer luftwaffeagnew sulfide extrinsicendothelial asheville latentcalve pituitary muscleavowal blunt boycottbeauregard tantalum hartmanoctile --1-627142907-9120026257=:58580-- From dhcwg-bounces@ietf.org Thu Oct 28 10:10:15 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 KAA15185 for ; Thu, 28 Oct 2004 10:10:15 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNBCr-00023H-7C for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 10:24:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNAsZ-00041s-8b; Thu, 28 Oct 2004 10:03:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNAmp-0001UI-Lk for dhcwg@megatron.ietf.org; Thu, 28 Oct 2004 09:57:55 -0400 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 JAA13736 for ; Thu, 28 Oct 2004 09:57:54 -0400 (EDT) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNB0t-0001iX-NT for dhcwg@ietf.org; Thu, 28 Oct 2004 10:12:29 -0400 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 28 Oct 2004 07:16:31 +0000 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9SDu9YJ009972; Thu, 28 Oct 2004 06:56:10 -0700 (PDT) Received: from volzw2k ([161.44.65.208]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMP95531; Thu, 28 Oct 2004 09:57:10 -0400 (EDT) From: "Bernie Volz" To: =?iso-8859-1?B?J0pJTk1FSSBUYXR1eWEgLyCQXy2+J0KNxic=?= , "'Grubmair Peter'" Subject: RE: [dhcwg] retransmission timeout in stateless DHCPv6 andpreference option ? Date: Thu, 28 Oct 2004 09:57:10 -0400 Organization: Cisco Message-ID: <000901c4bcf6$051a4180$d0412ca1@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 In-Reply-To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Content-Transfer-Encoding: quoted-printable Cc: "'Dhcwg \(E-mail\)'" X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Content-Transfer-Encoding: quoted-printable There's nothing I found in RFC 3315 that requires this. We were pretty = clear on what the SOLICIT behavior was, but weren't as clear in the INFORMATION-REQUEST case. I think you could go either way ... Follow the SOLICIT behavior and wait = the "first RT seconds" or take the first response. In the case where there = is a preference option and it specifies the highest preference (or where = there is no preference option), there would be no need to wait. If you wait, it = is only for 1 second based on the RFC specified values. I'd probably = recommend following the SOLICIT behavior. - Bernie > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20 > On Behalf Of JINMEI Tatuya / =90_=96=BE=92B=8D=C6 > Sent: Thursday, October 28, 2004 3:12 AM > To: Grubmair Peter > Cc: Dhcwg (E-mail) > Subject: Re: [dhcwg] retransmission timeout in stateless=20 > DHCPv6 andpreference option ? >=20 >=20 > >>>>> On Wed, 27 Oct 2004 15:03:31 +0200, > >>>>> Grubmair Peter said: >=20 > > If a statelesss dhcpv6 client receives a reply with=20 > preference option,=20 > > it has to wait until retransmission timer expires to select reply=20 > > highest preference. >=20 > Please let me check, which part of which RFC does specify=20 > this behavior? >=20 > Thanks, >=20 > JINMEI, Tatuya > Communication Platform Lab. > Corporate R&D Center,=20 > Toshiba Corp. > jinmei@isl.rdc.toshiba.co.jp >=20 > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg >=20 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From AmmarMcdanel@computerweekly.com Thu Oct 28 12:58: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 MAA18935 for ; Thu, 28 Oct 2004 12:58: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 1CNDpI-0003jx-Tf for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 13:12:42 -0400 Received: from [220.90.135.20] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1CNDbC-0002S3-KG for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 12:58:07 -0400 From: "Marshae Bosarge" To: dhcwg-web-archive@ietf.org Subject: Fwd: I need your help... Date: Thu, 28 Oct 2004 23:49:53 +0600 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: X-Spam-Score: 9.2 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: quoted-printable The danger could not be imminent?=20





Çîälis definetely = better then Vïägrå
..can last for 2 days
..You can have alcohol with Cïalís
..improves sexual performances twice better then Viagrâ
..it costs much cheaper than Pfízër Vï@grâ
Get ÇIÁLÏS (SÛPÈR VIÃGRÅ= ) here










No msg What was, then, the mystery of this submarine craft, of which the whole wo= rld vainly sought an explanation? What kind of beings existed in this stra= nge boat? What mechanical agent caused its prodigious speed?:=20 From dhcwg-bounces@ietf.org Thu Oct 28 15:47: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 PAA27106 for ; Thu, 28 Oct 2004 15:47:38 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNGTQ-0007ir-7s for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 16:02:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNCpV-000760-VE; Thu, 28 Oct 2004 12:08:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNC5M-0005nu-GL for dhcwg@megatron.ietf.org; Thu, 28 Oct 2004 11:21:08 -0400 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 LAA25490 for ; Thu, 28 Oct 2004 11:21:06 -0400 (EDT) Received: from mxs1.siemens.at ([194.138.12.131]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNCJO-0004cS-6V for dhcwg@ietf.org; Thu, 28 Oct 2004 11:35:42 -0400 Received: from vies1k7x.sie.siemens.at ([158.226.129.83]) by mxs1.siemens.at with ESMTP id i9SFKQT8006128 for ; Thu, 28 Oct 2004 17:20:26 +0200 Received: from vies141a.sie.siemens.at (vies1kbx.sie.siemens.at [158.226.135.174]) by vies1k7x.sie.siemens.at (8.12.10/8.12.1) with ESMTP id i9SFKQ45000328 for ; Thu, 28 Oct 2004 17:20:26 +0200 Received: by vies141a.sie.siemens.at with Internet Mail Service (5.5.2653.19) id ; Thu, 28 Oct 2004 17:22:59 +0200 Message-ID: <4D50D5110555D5119F270800062B41650532AC50@viee10pa.erd.siemens.at> From: Grubmair Peter To: "'Bernie Volz'" Subject: RE: [dhcwg] retransmission timeout in stateless DHCPv6 andprefere nce option ? Date: Thu, 28 Oct 2004 17:18:06 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Content-Transfer-Encoding: quoted-printable Cc: "Dhcwg \(E-mail\)" X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Content-Transfer-Encoding: quoted-printable Hi bernie, thank you for your reply, I will use your proposal and implement according 17.1.2 from RFC 3315. best regards Peter -----Original Message----- From: Bernie Volz [mailto:volz@cisco.com] Sent: Donnerstag, 28. Oktober 2004 15:57 To: 'JINMEI Tatuya / =90_-=BE'B=8D=C6'; 'Grubmair Peter' Cc: 'Dhcwg (E-mail)' Subject: RE: [dhcwg] retransmission timeout in stateless DHCPv6 andpreference option ? There's nothing I found in RFC 3315 that requires this. We were pretty = clear on what the SOLICIT behavior was, but weren't as clear in the INFORMATION-REQUEST case. I think you could go either way ... Follow the SOLICIT behavior and = wait the "first RT seconds" or take the first response. In the case where there = is a preference option and it specifies the highest preference (or where = there is no preference option), there would be no need to wait. If you wait, it = is only for 1 second based on the RFC specified values. I'd probably = recommend following the SOLICIT behavior. - Bernie > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20 > On Behalf Of JINMEI Tatuya / =90_-=BE'B=8D=C6 > Sent: Thursday, October 28, 2004 3:12 AM > To: Grubmair Peter > Cc: Dhcwg (E-mail) > Subject: Re: [dhcwg] retransmission timeout in stateless=20 > DHCPv6 andpreference option ? >=20 >=20 > >>>>> On Wed, 27 Oct 2004 15:03:31 +0200, > >>>>> Grubmair Peter said: >=20 > > If a statelesss dhcpv6 client receives a reply with=20 > preference option,=20 > > it has to wait until retransmission timer expires to select reply=20 > > highest preference. >=20 > Please let me check, which part of which RFC does specify=20 > this behavior? >=20 > Thanks, >=20 > JINMEI, Tatuya > Communication Platform Lab. > Corporate R&D Center,=20 > Toshiba Corp. > jinmei@isl.rdc.toshiba.co.jp >=20 > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg >=20 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Oct 28 15:52: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 PAA27960 for ; Thu, 28 Oct 2004 15:52:37 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNGYE-0007ua-3X for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 16:07:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNCsp-0001ol-01; Thu, 28 Oct 2004 12:12:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNCHf-0002VE-VP for dhcwg@megatron.ietf.org; Thu, 28 Oct 2004 11:33:52 -0400 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 LAA28450 for ; Thu, 28 Oct 2004 11:33:49 -0400 (EDT) Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNCVk-0005cn-9Z for dhcwg@ietf.org; Thu, 28 Oct 2004 11:48:25 -0400 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-1.cisco.com with ESMTP; 28 Oct 2004 08:44:42 -0700 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9SFX3YJ011657; Thu, 28 Oct 2004 08:33:04 -0700 (PDT) Received: from rdroms-w2k01.cisco.com ([161.44.65.190]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMQ04834; Thu, 28 Oct 2004 11:33:02 -0400 (EDT) Message-Id: <4.3.2.7.2.20041028112952.023747c0@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 28 Oct 2004 11:33:00 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 1.3 (+) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Subject: [dhcwg] IMPORTANT!!! dhc WG meeting now Tue AM X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 1.3 (+) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Please be aware that, as of the most recent IETF 61 agenda http://ietf.org/meetings/agenda_61.html (updated 10/27), the dhc WG is now scheduled to meet: TUESDAY, November 9, 2004 0900-1130 Morning Sessions INT dhc Dynamic Host Configuration WG * RTG mpls Multiprotocol LabelSwitching WG SEC btns Better-Than-Nothing Security BOF SEC ltans Long-Term Archive and Notary Services WG TSV ippm IP Performance Metrics WG TSV sipping Session Initiation Protocol WG - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From Stahlxvd@softcafe.net Thu Oct 28 16:42: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 QAA07422; Thu, 28 Oct 2004 16:42:27 -0400 (EDT) Received: from c-24-12-206-226.client.comcast.net ([24.12.206.226]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNHKS-0002HR-3i; Thu, 28 Oct 2004 16:57:06 -0400 Received: from mayflower.netscope.net (mayflower.netscope.net [0.159.96.160]) by 24.12.206.226 with ESMTP id <22873978734167.GRJS98586.butane@ciudad.com.ar> for ; Thu, 28 Oct 2004 23:38:40 +0300 Date: Thu, 28 Oct 2004 13:33:40 -0700 From: "Rolando Bishop" Reply-To: "Rolando Bishop" Message-ID: <059240h701y7397f65b7441c2b2975@jejune> To: Eugene Subject: happiness X-Mailer: placate cookery borroughs Organization: QUALCOMM Windows Eudora Version 5.1 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="4-435290792-8366588140=:54006" X-Spam-Score: 9.1 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 --4-435290792-8366588140=:54006 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable --4-435290792-8366588140=:54006 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable
=



unsubscribe<= /A>




dozen calcuttaexigent disneyland klaxonambrosia postcard mockernutgubernatorial palette seismographcraftsmen inexhaustible slaughterhousedeus lunary l'oeilhorowitz methacrylate jansenistsketchbook secede usvoluminous bloodroot fungiindy --4-435290792-8366588140=:54006-- From Piperarcn@tech.de Thu Oct 28 17:39:34 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 RAA18781; Thu, 28 Oct 2004 17:39:33 -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 1CNIDa-0005ey-JM; Thu, 28 Oct 2004 17:54:13 -0400 Received: from tony08-123-12.inter.net.il ([80.230.123.12]) by mx2.foretec.com with smtp (Exim 4.24) id 1CNHzJ-0003G7-F4; Thu, 28 Oct 2004 17:39:19 -0400 Received: from evolve.chink.com ([10.54.15.128]) by gp33-u56.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Thu, 28 Oct 2004 15:30:10 -0700 Received: from apj5-bucket3.Z2enq.com (nowise2 [196.248.218.129]) by gust.n3.com (0.05.6/8.35.1) with ESMTP id y6WH2vq74205 for ; Thu, 28 Oct 2004 23:30:10 +0100 GMT Received: (from z1strategy@localhost) by xnj3-snobbish8.y8uro.com (1.45.2/7.48.9) id o2JX3sh14142; Thu, 28 Oct 2004 19:37:10 -0300 GMT X-Authentication-Warning: xsl8-uphold6.e3ryv.com: z9schuster set sender to Piperarcn@tech.de using -f MIME-Version: 1.0 Date: Fri, 29 Oct 2004 02:38:10 +0400 From: Fritz Blackburn Subject: Microsoft Windows XP Professional update To: cfrg-request@ietf.org Message-Id: Content-Type: multipart/alternative; boundary="--3-102875449-0271124536=:16871" X-Spam-Score: 13.3 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 ----3-102875449-0271124536=:16871 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable W1ND0WS magazine : Review results
After a thorough comparison of the various retailers,By far the Best 0ffer= is:

X..P PR0 + 0FF1CE X..P PR0 - $80 (S@VE 420$)

Full Reviews Here=



simpson mallowcurtsey accomplish bellboybayberry privilege doriaclarke bitumen hewettbetel buzz deferralerror burgundy bundydissociate brothel ivanoperatic cooperate parliamentarianwith caliber bacterialaddendum ----3-102875449-0271124536=:16871-- From dhcwg-bounces@ietf.org Thu Oct 28 19:35:18 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 TAA12848 for ; Thu, 28 Oct 2004 19:35:18 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNK1l-0004DG-6l for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 19:49:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNHH3-0001dv-Mn; Thu, 28 Oct 2004 16:53:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNFeN-0003lT-2m for dhcwg@megatron.ietf.org; Thu, 28 Oct 2004 15:09:31 -0400 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 PAA18923 for ; Thu, 28 Oct 2004 15:09:29 -0400 (EDT) Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNFsU-0005Ei-6j for dhcwg@ietf.org; Thu, 28 Oct 2004 15:24:06 -0400 Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i9SJ8u716966; Thu, 28 Oct 2004 15:08:56 -0400 (EDT) Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 28 Oct 2004 15:08:58 -0400 Message-ID: <591B780D9676844E8A704B5B013FFE920387C3BD@zrc2hxm1.corp.nortel.com> From: "Kuntal Chowdhury" To: Bernie Volz , "'Ralph Droms'" Subject: RE: [dhcwg] BCMCS server option drafts Date: Thu, 28 Oct 2004 15:08:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 2d133cc328f58695161c98bb4f4dc213 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 4515df9441674711565101d9d5c4f63f Hello Bernie, Thanks for the response. I guess what is not clear to me is how a DHCP client requests vendor specific information from the DHCP server: " - A Client includes OPTION_VENDOR_CLASS to identify itself. - A Client MAY include OPTION_VENDOR_OPTS if it has vendor specific data (other than classing information) to communicate. - A Server includes OPTION_VENDOR_OPTS for matching enterprise IDs (and class data, if appropriate). This is only REQUIRED if the ORO includes the OPTION_VENDOR_OPTS code (the ORO doesn't say which vendors; that is handled by OPTION_VENDOR_CLASS). " Second bullet seems to say that the DHCP client includes OPTION_VENDOR_OPTS to convey some vendor specific information to the DHCP server beside the vendor class info (which is in OPTION_VENDOR_CLASS). It does not state that OPTION_VENDOR_OPTS is included in a DHCP message (such as information request) to REQUEST for vendor specific info from the server. It is true that opcode for OPTION_VENDOR_OPTS can be included in ORO, but that won't necessarily indicate to the server which vendor specific codes it needs to return to the client. Also, the format of the OPTION_VENDOR_OPTS when it appears in the REQUEST message is unclear. A clear description of how to use OPTION_VENDOR_OPTS to request vendor specific information (such as broadcast server address) will be required by SDOs such as 3GPP2. Regards, Kuntal >-----Original Message----- >From: Bernie Volz [mailto:volz@cisco.com] >Sent: Wednesday, October 27, 2004 8:34 PM >To: Chowdhury, Kuntal [RICH1:2H18:EXCH]; 'Ralph Droms' >Cc: dhcwg@ietf.org >Subject: RE: [dhcwg] BCMCS server option drafts > > >Hi: > >I believe the original model was for OPTION_VENDOR_CLASS to be >similar to DHCPv4 Vendor class identifier option (option 60) >and for OPTION_VENDOR_OPTS to be similar to DHCPv4 Vendor >Specific Information (option 43). > >You might refer to draft-ietf-dhc-vendor-03.txt, while for >DHCPv4, it does have some additional information about how the >options might be used. That work is modeled on the DHCPv6 >options. In particular, see section 4: > >4. Vendor-Identifying Vendor-Specific Information Option > > DHCP clients and servers may use this option to exchange vendor- > specific information. Either party may send this option, as needed. > While a typical case might be for a client to send the > Vendor-Identifying Vendor Class option, to elicit a useful > Vendor-Identifying Vendor-Specific Information Option, there is no > requirement for such a flow. > >It would be good to get general agreement on this as you're >perhaps the first user. And, it would be best to set a >"standard" for others to follow. > >I kind of liked the DHCPv4 model, as it is much easier and >clearly to understand (and implement for clients and servers): >- A Client includes OPTION_VENDOR_CLASS to identify itself. >- A Client MAY include OPTION_VENDOR_OPTS if it has vendor >specific data (other than classing information) to communicate. >- A Server includes OPTION_VENDOR_OPTS for matching enterprise >IDs (and class data, if appropriate). This is only REQUIRED if >the ORO includes the OPTION_VENDOR_OPTS code (the ORO doesn't >say which vendors; that is handled by OPTION_VENDOR_CLASS). >- I'm not sure why a server would ever need to include >OPTION_VENDOR_CLASS, though perhaps it could tell the client >what implementation the server is so that perhaps the client >knows it could use some extended capabilities? Or, the server >could send back whatever the client sent to it? > >But, as draft-ietf-dhc-vendor-03.tx states, this is not the >only possible model. > >Note that in your case, I would assume that the >OPTION_VENDOR_CLASS would have your enterprise ID and some >class information to indicate what capabilities the client >supports (and therefore the server should provide >configuration for in the OPTION_VENDOR_OPTS). > >So, this is a good issue for the DHC WG to resolve and clarify >for a future RFC 3315bis. > >- Bernie > >> -----Original Message----- >> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] >> On Behalf Of Kuntal Chowdhury >> Sent: Wednesday, October 27, 2004 4:33 PM >> To: Ralph Droms; volz@cisco.com >> Cc: dhcwg@ietf.org >> Subject: RE: [dhcwg] BCMCS server option drafts >> >> >> I have a few questions on the possible use of DHCPv6 >> OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS to request vendor >> specific info: >> >> 1. Since the enterprise number is included in >> OPTION_VENDOR_OPTS, will it suffice to use only this option >> in the information request message from the DHCP client? Is >> the use of OPTION_VENDOR_CLASS mandatory while vendor >> specific options are requested? >> >> 2. Does the mere inclusion of OPTION_VENDOR_OPTS in the >> information request message indicate to the DHCP server that >> the DHCP client is requesting for some specific vendor >> specific options? >> >> 3. O-R-O has the format where each of requested option codes >> are listed in it. However, in OPTION_VENDOR_OPTS the >> encapsulated vendor-specific options field MUST be encoded as >> a sequence of code/length/value fields. What value does the >> DHCP client use while requesting for a vendor specific option? >> >> These things are not clearly defined in RFC3315. >> >> Regards, >> Kuntal >> >> >-----Original Message----- >> >From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On >> >Behalf Of Ralph Droms >> >Sent: Wednesday, October 27, 2004 2:29 PM >> >To: dhcwg@ietf.org >> >Subject: RE: [dhcwg] BCMCS server option drafts >> > >> > >> > >> >What about the deployment issue? The 3GGP2 specification will be >> >ratified in November, with deployment following soon. Some service >> >providers already have DHCP servers in place that must be >updated for >> >any new options. The options defined in the current drafts can >> >likely be supported without code changes to existing servers, >> >allowing for faster deployment. Use of a VIVSO sub-option would >> >require code changes to existing servers. How long would >it take to >> >deploy DHCP server that can support VIVSO? >> > >> >BTW, we need more discussion of this issue *soon* due to the time >> >constraints of the upcoming 3GPP2 standards process and deployment. >> > >> >- Ralph >> > >> >At 04:12 PM 10/21/2004 -0400, Bernie Volz wrote: >> >>Personally, I'd like to see the DHCPv4 VIVSO get deployed >> and pushing >> >>these options to using it would be a step at making this >> >happen (as one >> >>would expect 3GPP2 vendors to have some significant input to the >> >>decisions of DHCP server vendors). >> >> >> >>It also means that 3GPP2 is free to define other VIVSO >> options in the >> >>future within their own forum and need not go to the IETF >> >(and DHC WG). >> >>I suspect that this would provide much faster deployment >for them in >> >>the future. >> >> >> >>Also, the DHCPv6 OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS >> >are already >> >>there for DHCPv6. >> >> >> >>BTW, 3GPP2 already has an enterprise-id number: >> >> >> >>5535 >> >> 3rd Generation Partnership Project 2 (3GPP2) >> >> Allen Long >> >> along@cisco.com >> >> >> >>So, they'd be good to go! >> >> >> >>- Bernie >> >> >> >> > -----Original Message----- >> >> > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On >> >> > Behalf Of Ralph Droms >> >> > Sent: Thursday, October 21, 2004 2:35 PM >> >> > To: dhcwg@ietf.org >> >> > Subject: [dhcwg] BCMCS server option drafts >> >> > >> >> > >> >> > We need to have a short WG conversation about two options >> >that were >> >> > discussed at the WG meeting in San Diego. The outcome of the >> >> > conversation will be to determine consensus about taking >> on these >> >> > two >> >> > drafts: >> >> > >> >> > draft-chowdhury-dhc-bcmcv4-option-01.txt >> >> > draft-chowdhury-dhc-bcmcv6-option-01.txt >> >> > >> >> > as dhc WG work items or recommending that 3GPP2 define >> >> > vendor-identifying vendor-specific option (VIVSO; option code >> >> > 125) sub-options to carry the information described in >> the drafts. >> >> > >> >> > If the WG consensus is to take on the drafts as WG work items >> >> > drafts, are they acceptable as currently published? >> >> > >> >> > Because of the time constraints imposed by the 3GPP2 >> schedule, I'm >> >> > going to cut off discussion on this topic next Thursday, >> >10/28, and >> >> > determine WG consensus at that time. >> >> > >> >> > Here are some considerations for discussion: >> >> > >> >> > 3GPP2 has defined some vendor-specific sub-options, for >> >example, to >> >> > identify a MIP home agent for the DHCP client. >> >> > >> >> > A 3GPP2 client needs to specify to the DHCP server which >> >parameters >> >> > it needs - specifically, whether it needs to receive the BCMCS >> >> > servers. If the current drafts are adopted, the client >> can simply >> >> > use the parameter request list option (option code 55) for the >> >> > request. If a VIVSO sub-option is used, 3GPP2 would >> also define a >> >> > parameter request list sub-option. >> >> > >> >> > There is a deployment issue, as some service providers >> >already have >> >> > DHCP servers in place that must be updated for any new >> >options. Is >> >> > it the case that the options defined in the current >drafts can be >> >> > supported without code changes to existing servers? Use >> >of a VIVSO >> >> > sub-option would require code changes to existing servers. >> > How long >> >> > would it take to deploy DHCP server that can support VIVSO. >> >> > >> >> > BCMCS may be adopted across multiple technologies, so the >> >options in >> >> > the current drafts would not be specific to 3GPP2. >However, the >> >> > BCMCS specification has not adopted by other standards, >> yet, so we >> >> > may need to define additional options for related >> services in the >> >> > future if those services are not interoperable with the >> >3GPP2 BCMCS >> >> > service. >> >> > >> >> > CableLabs has one option with sub-options (RFC 3495) >rather than >> >> > multiple options because: >> >> > * wanted to avoid exhaustion of DHCP option code space; >> >perhaps less >> >> > of an issue with option code reclassification >> >> > * would have used VIVSO if available >> >> > * use of VIVSO with sub-options would give 3GPP2 freedom >> >to define new >> >> > sub-options on demand >> >> > Do these considerations have an impact on our decision >> >about how to >> >> > proceed with the 3GPP2 options? >> >> > >> >> > - Ralph >> >> > >> >> > >> >> > _______________________________________________ >> >> > dhcwg mailing list >> >> > dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg >> >> > >> > >> > >> >_______________________________________________ >> >dhcwg mailing list >> >dhcwg@ietf.org >> >https://www1.ietf.org/mailman/listinfo/dhcwg >> > >> > >> >> _______________________________________________ >> dhcwg mailing list >> dhcwg@ietf.org >> https://www1.ietf.org/mailman/listinfo/dhcwg >> > > > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Oct 28 20:04:21 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 UAA21235 for ; Thu, 28 Oct 2004 20:04:20 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNKTr-0006xp-9m for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 20:19:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNJ8T-00084E-Vx; Thu, 28 Oct 2004 18:52:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNGA0-0008PT-MB for dhcwg@megatron.ietf.org; Thu, 28 Oct 2004 15:42:12 -0400 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 PAA25732 for ; Thu, 28 Oct 2004 15:42:11 -0400 (EDT) Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNGO8-00076E-Cu for dhcwg@ietf.org; Thu, 28 Oct 2004 15:56:49 -0400 Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) id <0I6B00A01819QC@mailout1.samsung.com> for dhcwg@ietf.org; Fri, 29 Oct 2004 04:41:33 +0900 (KST) Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0I6B003XJ818NT@mailout1.samsung.com> for dhcwg@ietf.org; Fri, 29 Oct 2004 04:41:33 +0900 (KST) Received: from Alperyegin ([105.144.29.41]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0I6B00LW2816X4@mmp1.samsung.com> for dhcwg@ietf.org; Fri, 29 Oct 2004 04:41:32 +0900 (KST) Date: Thu, 28 Oct 2004 12:41:30 -0700 From: Alper Yegin To: dhcwg@ietf.org Message-id: <002701c4bd26$205513f0$291d9069@sisa.samsung.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Mailer: Microsoft Outlook, Build 10.0.2627 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7BIT Subject: [dhcwg] DHCP auth X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: 7BIT >From posted agenda: DHCP Authentication via EAP Mark Stapp 10 minutes Technical discussion It's been a while since we discussed this issue. Here is a relevant (now expired) I-D, FYI: http://www.watersprings.org/pub/id/draft-yegin-eap-boot-rfc3118-00.txt Meanwhile, I'm wondering the status of draft-ietf-dhc-v4-threat-analysis-02. Alper _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Thu Oct 28 20:12: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 UAA23609 for ; Thu, 28 Oct 2004 20:12:57 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNKcC-0007hl-Tc for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 20:27:37 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNJ9N-0001Gy-OZ; Thu, 28 Oct 2004 18:53:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNGC9-0001EX-K3; Thu, 28 Oct 2004 15:44:25 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26254; Thu, 28 Oct 2004 15:44:24 -0400 (EDT) Message-Id: <200410281944.PAA26254@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 28 Oct 2004 15:44:23 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-dual-stack-02.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : DHCP: IPv4 and IPv6 Dual-Stack Issues Author(s) : T. Chown, et al. Filename : draft-ietf-dhc-dual-stack-02.txt Pages : 13 Date : 2004-10-28 A node may have support for communications using IPv4 and/or IPv6 protocols. Such a node may wish to obtain IPv4 and/or IPv6 configuration settings via the Dynamic Host Configuration Protocol (DHCP). The original version of DHCP [1] designed for IPv4 has now been complemented by a new DHCPv6 [4] for IPv6. This document describes issues identified with dual IP version DHCP interactions, the most important aspect of which is how to handle potential problems in clients processing configuration information received from DHCPv4 and DHCPv6 servers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-dual-stack-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-dual-stack-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-dual-stack-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-28154902.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-dual-stack-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-dual-stack-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-28154902.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From dhcwg-bounces@ietf.org Thu Oct 28 20:15:15 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 UAA24530 for ; Thu, 28 Oct 2004 20:15:15 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNKeR-0007wd-7D for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 20:29:55 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNJ9V-0001Rs-UP; Thu, 28 Oct 2004 18:53:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNGCU-0001R5-06; Thu, 28 Oct 2004 15:44:46 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26344; Thu, 28 Oct 2004 15:44:44 -0400 (EDT) Message-Id: <200410281944.PAA26344@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 28 Oct 2004 15:44:44 -0400 Cc: dhcwg@ietf.org Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-stateless-dhcpv6-renumbering-02.txt X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : Renumbering Requirements for Stateless DHCPv6 Author(s) : T. Chown, et al. Filename : draft-ietf-dhc-stateless-dhcpv6-renumbering-02.txt Pages : 8 Date : 2004-10-28 IPv6 hosts using Stateless Address Autoconfiguration are able to automatically configure their IPv6 address and default router settings. However, further settings are not available. If such hosts wish to automatically configure their DNS, NTP or other specific settings the stateless variant of the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) could be used. This combination of Stateless Address Autoconfiguration and stateless DHCPv6 could be used quite commonly in IPv6 networks. However, hosts using such a combination currently have no means by which to be informed of changes in stateless DHCPv6 option settings, e.g. the addition of a new NTP server address, changes in DNS search paths, or full site renumbering. This document is presented as a problem statement from which a solution should be proposed in a subsequent document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-stateless-dhcpv6-renumbering-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-dhc-stateless-dhcpv6-renumbering-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-dhc-stateless-dhcpv6-renumbering-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-10-28154907.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-stateless-dhcpv6-renumbering-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-stateless-dhcpv6-renumbering-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-28154907.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --NextPart-- From dhcwg-bounces@ietf.org Thu Oct 28 21:14:12 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 VAA06671 for ; Thu, 28 Oct 2004 21:14:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNLZT-0003XW-5o for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 21:28:52 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNJC7-0005Kn-Ps; Thu, 28 Oct 2004 18:56:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNGL2-00073K-NL for dhcwg@megatron.ietf.org; Thu, 28 Oct 2004 15:53:37 -0400 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 PAA28181 for ; Thu, 28 Oct 2004 15:53:35 -0400 (EDT) Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNGZ9-0007vq-9w for dhcwg@ietf.org; Thu, 28 Oct 2004 16:08:13 -0400 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 28 Oct 2004 13:02:23 -0700 Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9SJqvYJ023759; Thu, 28 Oct 2004 12:52:58 -0700 (PDT) Received: from volzw2k ([161.44.65.208]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMQ33185; Thu, 28 Oct 2004 15:52:59 -0400 (EDT) From: "Bernie Volz" To: "'Kuntal Chowdhury'" , "'Ralph Droms'" Subject: RE: [dhcwg] BCMCS server option drafts Date: Thu, 28 Oct 2004 15:52:59 -0400 Organization: Cisco Message-ID: <002801c4bd27$b9f6a5e0$d0412ca1@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 In-Reply-To: <591B780D9676844E8A704B5B013FFE920387C3BD@zrc2hxm1.corp.nortel.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 9c7d7a899dc8f3389bf7ace6f0ad8e29 Content-Transfer-Encoding: quoted-printable Cc: dhcwg@ietf.org, "'josh Littlefield'" X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 4c358d334afcd91b425d436ca5722f22 Content-Transfer-Encoding: quoted-printable Hi: Good timing ... I just finished a conversation with Ralph on this issue. Basically, Ralph feels that what comes in from the client *COULD* = trigger what goes back, but there's no requirement for this. And if there is a trigger, it could be anything - it could be from OPTION_VENDOR_CLASS or OPTION_VENDOR_OPTS or some other data (such as USER_CLASS, the link the client is on, etc). For example, in the 3GPP2 environment, it may well be that the DHCP(v6) server is ONLY servicing 3GPP2 clients so it could be configured to = *ALWAYS* send back the OPTION_VENDOR_OPTS regardless of what the client sends in. Note that if the server sends back a OPTION_VENDOR_OPTS (or OPTION_VENDOR_CLASS) with information that the client doesn't know about (ie, enterprise ID isn't a known value), the client MUST ignore that = data (just like if it received an unknown option). If this will be used in environments where it is known that all clients = will need this information, simply require the servers to be configured to = send it. A particular client that doesn't support the functionality will just ignore the information. If this will be used in mixed environments where many different client = types will exist, some which will never want this information (and there are = good reasons not to send it to them), you could define a mechanism to trigger = a server to send it. You might do this using a OPTION_VENDOR_CLASS to, for example, communicate that this is a 3GPP2 device interested in BCMCS service. Or simply that is is a 3GPP2 device. You could also use the OPTION_VENDOR_OPTS to do this (client->server). But, even if you did = this, a server may still be configured to send it unconditionally. - Bernie > -----Original Message----- > From: Kuntal Chowdhury [mailto:chowdury@nortelnetworks.com]=20 > Sent: Thursday, October 28, 2004 3:09 PM > To: Bernie Volz; 'Ralph Droms' > Cc: dhcwg@ietf.org > Subject: RE: [dhcwg] BCMCS server option drafts >=20 >=20 > Hello Bernie, >=20 > Thanks for the response. I guess what is not clear to me is=20 > how a DHCP client requests vendor specific information from=20 > the DHCP server: >=20 > " > - A Client includes OPTION_VENDOR_CLASS to identify itself. > - A Client MAY include OPTION_VENDOR_OPTS if it has vendor=20 > specific data (other than classing information) to communicate. > - A Server includes OPTION_VENDOR_OPTS for matching=20 > enterprise IDs (and class data, if appropriate). This is only=20 > REQUIRED if the ORO includes the OPTION_VENDOR_OPTS code (the=20 > ORO doesn't say which vendors; that is handled by=20 > OPTION_VENDOR_CLASS). " >=20 > Second bullet seems to say that the DHCP client includes=20 > OPTION_VENDOR_OPTS to convey some vendor specific information=20 > to the DHCP server beside the vendor class info (which is in=20 > OPTION_VENDOR_CLASS). It does not state that=20 > OPTION_VENDOR_OPTS is included in a DHCP message (such as information > request) to REQUEST for vendor specific info from the server.=20 > It is true that opcode for OPTION_VENDOR_OPTS can be included=20 > in ORO, but that won't necessarily indicate to the server=20 > which vendor specific codes it needs to return to the client.=20 > Also, the format of the OPTION_VENDOR_OPTS when it appears in=20 > the REQUEST message is unclear. >=20 > A clear description of how to use OPTION_VENDOR_OPTS to=20 > request vendor specific information (such as broadcast server=20 > address) will be required by SDOs such as 3GPP2. >=20 > Regards, > Kuntal >=20 >=20 > >-----Original Message----- > >From: Bernie Volz [mailto:volz@cisco.com] > >Sent: Wednesday, October 27, 2004 8:34 PM > >To: Chowdhury, Kuntal [RICH1:2H18:EXCH]; 'Ralph Droms' > >Cc: dhcwg@ietf.org > >Subject: RE: [dhcwg] BCMCS server option drafts > > > > > >Hi: > > > >I believe the original model was for OPTION_VENDOR_CLASS to be > >similar to DHCPv4 Vendor class identifier option (option 60)=20 > >and for OPTION_VENDOR_OPTS to be similar to DHCPv4 Vendor=20 > >Specific Information (option 43). > > > >You might refer to draft-ietf-dhc-vendor-03.txt, while for > >DHCPv4, it does have some additional information about how the=20 > >options might be used. That work is modeled on the DHCPv6=20 > >options. In particular, see section 4: > > > >4. Vendor-Identifying Vendor-Specific Information Option > > > > DHCP clients and servers may use this option to exchange vendor- > > specific information. Either party may send this option,=20 > as needed. > > While a typical case might be for a client to send the > > Vendor-Identifying Vendor Class option, to elicit a useful > > Vendor-Identifying Vendor-Specific Information Option, there is no > > requirement for such a flow. > > > >It would be good to get general agreement on this as you're > >perhaps the first user. And, it would be best to set a=20 > >"standard" for others to follow. > > > >I kind of liked the DHCPv4 model, as it is much easier and > >clearly to understand (and implement for clients and servers): > >- A Client includes OPTION_VENDOR_CLASS to identify itself. > >- A Client MAY include OPTION_VENDOR_OPTS if it has vendor=20 > >specific data (other than classing information) to communicate. > >- A Server includes OPTION_VENDOR_OPTS for matching enterprise=20 > >IDs (and class data, if appropriate). This is only REQUIRED if=20 > >the ORO includes the OPTION_VENDOR_OPTS code (the ORO doesn't=20 > >say which vendors; that is handled by OPTION_VENDOR_CLASS). > >- I'm not sure why a server would ever need to include=20 > >OPTION_VENDOR_CLASS, though perhaps it could tell the client=20 > >what implementation the server is so that perhaps the client=20 > >knows it could use some extended capabilities? Or, the server=20 > >could send back whatever the client sent to it? > > > >But, as draft-ietf-dhc-vendor-03.tx states, this is not the > >only possible model. > > > >Note that in your case, I would assume that the > >OPTION_VENDOR_CLASS would have your enterprise ID and some=20 > >class information to indicate what capabilities the client=20 > >supports (and therefore the server should provide=20 > >configuration for in the OPTION_VENDOR_OPTS). > > > >So, this is a good issue for the DHC WG to resolve and clarify > >for a future RFC 3315bis. > > > >- Bernie > > > >> -----Original Message----- > >> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On=20 > >> Behalf Of Kuntal Chowdhury > >> Sent: Wednesday, October 27, 2004 4:33 PM > >> To: Ralph Droms; volz@cisco.com > >> Cc: dhcwg@ietf.org > >> Subject: RE: [dhcwg] BCMCS server option drafts > >>=20 > >>=20 > >> I have a few questions on the possible use of DHCPv6=20 > >> OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS to request=20 > vendor specific=20 > >> info: > >>=20 > >> 1. Since the enterprise number is included in OPTION_VENDOR_OPTS,=20 > >> will it suffice to use only this option in the information request=20 > >> message from the DHCP client? Is the use of OPTION_VENDOR_CLASS=20 > >> mandatory while vendor specific options are requested? > >>=20 > >> 2. Does the mere inclusion of OPTION_VENDOR_OPTS in the=20 > information=20 > >> request message indicate to the DHCP server that the DHCP=20 > client is=20 > >> requesting for some specific vendor specific options? > >> > >> 3. O-R-O has the format where each of requested option codes are=20 > >> listed in it. However, in OPTION_VENDOR_OPTS the encapsulated=20 > >> vendor-specific options field MUST be encoded as a sequence of=20 > >> code/length/value fields. What value does the DHCP client=20 > use while=20 > >> requesting for a vendor specific option? > >>=20 > >> These things are not clearly defined in RFC3315. > >>=20 > >> Regards, > >> Kuntal > >>=20 > >> >-----Original Message----- > >> >From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On > >> >Behalf Of Ralph Droms > >> >Sent: Wednesday, October 27, 2004 2:29 PM > >> >To: dhcwg@ietf.org > >> >Subject: RE: [dhcwg] BCMCS server option drafts > >> > > >> > > >> > > >> >What about the deployment issue? The 3GGP2 specification will be > >> >ratified in November, with deployment following soon. =20 > Some service=20 > >> >providers already have DHCP servers in place that must be=20 > >updated for > >> >any new options. The options defined in the current drafts can > >> >likely be supported without code changes to existing servers,=20 > >> >allowing for faster deployment. Use of a VIVSO sub-option would=20 > >> >require code changes to existing servers. How long would=20 > >it take to > >> >deploy DHCP server that can support VIVSO? > >> > > >> >BTW, we need more discussion of this issue *soon* due to the time > >> >constraints of the upcoming 3GPP2 standards process and=20 > deployment. > >> > > >> >- Ralph > >> > > >> >At 04:12 PM 10/21/2004 -0400, Bernie Volz wrote: > >> >>Personally, I'd like to see the DHCPv4 VIVSO get deployed > >> and pushing > >> >>these options to using it would be a step at making this > >> >happen (as one > >> >>would expect 3GPP2 vendors to have some significant input to the > >> >>decisions of DHCP server vendors). > >> >> > >> >>It also means that 3GPP2 is free to define other VIVSO > >> options in the > >> >>future within their own forum and need not go to the IETF > >> >(and DHC WG). > >> >>I suspect that this would provide much faster deployment > >for them in > >> >>the future. > >> >> > >> >>Also, the DHCPv6 OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS > >> >are already > >> >>there for DHCPv6. > >> >> > >> >>BTW, 3GPP2 already has an enterprise-id number: > >> >> > >> >>5535 > >> >> 3rd Generation Partnership Project 2 (3GPP2) > >> >> Allen Long > >> >> along@cisco.com > >> >> > >> >>So, they'd be good to go! > >> >> > >> >>- Bernie > >> >> > >> >> > -----Original Message----- > >> >> > From: dhcwg-bounces@ietf.org=20 > [mailto:dhcwg-bounces@ietf.org] On > >> >> > Behalf Of Ralph Droms > >> >> > Sent: Thursday, October 21, 2004 2:35 PM > >> >> > To: dhcwg@ietf.org > >> >> > Subject: [dhcwg] BCMCS server option drafts > >> >> > > >> >> > > >> >> > We need to have a short WG conversation about two options > >> >that were > >> >> > discussed at the WG meeting in San Diego. The outcome of the > >> >> > conversation will be to determine consensus about taking > >> on these > >> >> > two > >> >> > drafts: > >> >> > > >> >> > draft-chowdhury-dhc-bcmcv4-option-01.txt > >> >> > draft-chowdhury-dhc-bcmcv6-option-01.txt > >> >> > > >> >> > as dhc WG work items or recommending that 3GPP2 define > >> >> > vendor-identifying vendor-specific option (VIVSO; option code > >> >> > 125) sub-options to carry the information described in > >> the drafts. > >> >> > > >> >> > If the WG consensus is to take on the drafts as WG work items > >> >> > drafts, are they acceptable as currently published? > >> >> > > >> >> > Because of the time constraints imposed by the 3GPP2 > >> schedule, I'm > >> >> > going to cut off discussion on this topic next Thursday, > >> >10/28, and > >> >> > determine WG consensus at that time. > >> >> > > >> >> > Here are some considerations for discussion: > >> >> > > >> >> > 3GPP2 has defined some vendor-specific sub-options, for > >> >example, to > >> >> > identify a MIP home agent for the DHCP client. > >> >> > > >> >> > A 3GPP2 client needs to specify to the DHCP server which > >> >parameters > >> >> > it needs - specifically, whether it needs to receive the BCMCS > >> >> > servers. If the current drafts are adopted, the client > >> can simply > >> >> > use the parameter request list option (option code=20 > 55) for the=20 > >> >> > request. If a VIVSO sub-option is used, 3GPP2 would > >> also define a > >> >> > parameter request list sub-option. > >> >> > > >> >> > There is a deployment issue, as some service providers > >> >already have > >> >> > DHCP servers in place that must be updated for any new > >> >options. Is > >> >> > it the case that the options defined in the current > >drafts can be > >> >> > supported without code changes to existing servers? Use > >> >of a VIVSO > >> >> > sub-option would require code changes to existing servers. > >> > How long > >> >> > would it take to deploy DHCP server that can support VIVSO. > >> >> > > >> >> > BCMCS may be adopted across multiple technologies, so the > >> >options in > >> >> > the current drafts would not be specific to 3GPP2. > >However, the > >> >> > BCMCS specification has not adopted by other standards, > >> yet, so we > >> >> > may need to define additional options for related > >> services in the > >> >> > future if those services are not interoperable with the > >> >3GPP2 BCMCS > >> >> > service. > >> >> > > >> >> > CableLabs has one option with sub-options (RFC 3495) > >rather than > >> >> > multiple options because: > >> >> > * wanted to avoid exhaustion of DHCP option code space; > >> >perhaps less > >> >> > of an issue with option code reclassification > >> >> > * would have used VIVSO if available > >> >> > * use of VIVSO with sub-options would give 3GPP2 freedom > >> >to define new > >> >> > sub-options on demand > >> >> > Do these considerations have an impact on our decision > >> >about how to > >> >> > proceed with the 3GPP2 options? > >> >> > > >> >> > - Ralph > >> >> > > >> >> > > >> >> > _______________________________________________ > >> >> > dhcwg mailing list > >> >> > dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg > >> >> > > >> > > >> > > >> >_______________________________________________ > >> >dhcwg mailing list > >> >dhcwg@ietf.org > >> >https://www1.ietf.org/mailman/listinfo/dhcwg > >> > > >> > > >>=20 > >> _______________________________________________ > >> dhcwg mailing list > >> dhcwg@ietf.org > >> https://www1.ietf.org/mailman/listinfo/dhcwg > >>=20 > > > > > > >=20 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From Doughertybrca@bestlink.net Thu Oct 28 21:17:15 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 VAA07520; Thu, 28 Oct 2004 21:17:15 -0400 (EDT) Received: from net24-164-106-225.neo.rr.com ([24.164.106.225]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNLcQ-0003hq-Uf; Thu, 28 Oct 2004 21:31:55 -0400 Received: from yoghurt.jury.buffymail.com (cerulean.dunbar.buffymail.com [245.209.134.118]) by andrea.fitzgerald.buffymail.com (1.65.9q9/3.07.8/b: disparate.kp,v 1.66 2972/36/52 57:35:29 banpzpf1 Exp $) with ESMTP id h6GE3uq86446 for ; Fri, 29 Oct 2004 07:16:04 +0600 GMT Received: from nklqyioi188.forsook.buffymail.com (llgzlire123.crossarm.buffymail.com [229.16.99.168]) by harvestman.rd.buffymail.com (4.16.6t8/6.51.5/v: drunk.ve,v 1.66 3358/85/96 63:58:16 aqvjchf1 Exp $) with SMTP id h6LN5Km07324 for ; Thu, 28 Oct 2004 20:15:04 -0500 GMT From: VV_FD_TRs@buffymail.com Received: from bertie.j.staid.buffymail.com ([8.57.112.164]) by fnahmdzs409.drummond.buffymail.com (ADELD 2.5.2.11) with SMTP id M9624693637323798677 for ; Fri, 29 Oct 2004 00:14:04 -0100 Received: from courtesy ([85.44.250.208) by lad.algebra.evansville.buffymail.com with Microsoft SMTPSVC(5.0.0455.8861); Fri, 29 Oct 2004 02:14:04 +0100 To: Subject: help your sister in pain Date: Fri, 29 Oct 2004 04:17:04 +0300 Message-ID: <021y98e84gh7$f616f131$g1p0g7o4@berg.helpmate.buffymail.com> MIME-Version: 1.0 X-Mailer: The Bat! (v1.52f) Business Content-type: multipart/alternative; boundary="----=_NextPart_0-366238648-2959991436=:05322" X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 16.8 (++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 97adf591118a232206bdb5a27b217034 This is a multi-part message in MIME format. ------=_NextPart_0-366238648-2959991436=:05322 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -------------------------------------------------------------------------= ------- ------=_NextPart_0-366238648-2959991436=:05322 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable




Remove




= roughen pietysheraton nuisance digestionchicago sachs shan'tbanish coon taxonomicfmc battle cameschnabel cattleman twentycoastal teat extollingsawtimber burmese acquittingrelief skulk morselenterprise ------=_NextPart_0-366238648-2959991436=:05322-- From dhcwg-bounces@ietf.org Thu Oct 28 22:19:12 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 WAA22789 for ; Thu, 28 Oct 2004 22:19:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNMaQ-0008Gk-3X for dhcwg-web-archive@ietf.org; Thu, 28 Oct 2004 22:33:54 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNJwv-0000px-8M; Thu, 28 Oct 2004 19:44:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNHrH-00022X-Hq for dhcwg@megatron.ietf.org; Thu, 28 Oct 2004 17:30:59 -0400 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 RAA16786; Thu, 28 Oct 2004 17:30:57 -0400 (EDT) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNI5P-00058p-RF; Thu, 28 Oct 2004 17:45:37 -0400 Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 28 Oct 2004 17:53:06 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i9SLUPUD017099; Thu, 28 Oct 2004 17:30:26 -0400 (EDT) Received: from rdroms-w2k01.cisco.com ([161.44.65.190]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMQ42825; Thu, 28 Oct 2004 17:30:24 -0400 (EDT) Message-Id: <4.3.2.7.2.20041028172738.023a0008@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 28 Oct 2004 17:30:06 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Cc: agenda@ietf.org Subject: [dhcwg] Tentative agenda for dhc WG meeting at IETF 61 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Here is the latest draft agenda for the dhc WG meeting at IETF 61. NOTE CHANGE OF DATE TO TUE, 2004-11-09!!! - Ralph DHC WG agenda - IETF 61 0900 Tue 2004-11-09 (tentative) (Last revised 2004-10-28 05:25 PM) ---------------------------------- Administrivia Ralph Droms 10 minutes Agenda bashing; blue sheets; scribe; Jabber scribe Request for milestones for dhc WG drafts DNS zone suffix option for DHCPv6 Renxiang Yan 10 minutes Accept as dhc WG work item? Reclassifying DHCPv4 Options TBD 10 minutes How to implement the process after RFC is published? Vendor-Specific Information Suboption Mark Stapp 10 minutes Ready for WG last call? DHCP Authentication via EAP Mark Stapp 10 minutes Technical discussion Lifetime Option for DHCPv6 Stig Venaas 10 minutes Ready for WG last call? Anycast Address Assignment using DHCPv6 Syam Madanapalli 10 minutes Accept as dhc WG work item? Source Address Selection Policy option for DHCPv6 A. Matsumoto 10 minutes (available as http://www.nttv6.net/~arifumi/draft-hirotaka-dhc-source-address-selection-opt-00.txt) Accept as dhc WG work item? DHCPv6 Relay Agent Information Option Wing Cheong Lau 10 minutes Accept as dhc WG work item? DHCP-DNS interaction Bernie Volz 30 minutes Technical discussion ----------- 120 minutes _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Oct 29 00:05: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 AAA05923 for ; Fri, 29 Oct 2004 00:05:40 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNOFS-0003uG-AK for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 00:20:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNNiR-0003HQ-C8; Thu, 28 Oct 2004 23:46:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNNVq-0005zG-QU for dhcwg@megatron.ietf.org; Thu, 28 Oct 2004 23:33:15 -0400 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 XAA03313; Thu, 28 Oct 2004 23:33:13 -0400 (EDT) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNNk4-0002tu-1L; Thu, 28 Oct 2004 23:47:56 -0400 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 28 Oct 2004 23:55:26 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9T3Wgps021740; Thu, 28 Oct 2004 23:32:42 -0400 (EDT) Received: from rdroms-w2k01.cisco.com (sjc-vpn2-660.cisco.com [10.21.114.148]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMQ59907; Thu, 28 Oct 2004 23:32:40 -0400 (EDT) Message-Id: <4.3.2.7.2.20041028233131.0276e800@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 28 Oct 2004 23:32:36 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: agenda@ietf.org Subject: [dhcwg] Tentative agenda for dhc WG meeting at IETF 61 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Here is the latest draft agenda for the dhc WG meeting at IETF 61. - Ralph DHC WG agenda - IETF 61 0900 Tue 2004-11-09 (tentative) (Last revised 2004-10-28 11:29 PM) ---------------------------------- Administrivia Ralph Droms 10 minutes Agenda bashing; blue sheets; scribe; Jabber scribe Request for milestones for dhc WG drafts DNS zone suffix option for DHCPv6 Renxiang Yan 10 minutes Accept as dhc WG work item? Reclassifying DHCPv4 Options TBD 10 minutes How to implement the process after RFC is published? Vendor-Specific Information Suboption Mark Stapp 10 minutes Ready for WG last call? DHCP Authentication via EAP Mark Stapp 10 minutes Technical discussion Lifetime Option for DHCPv6 Stig Venaas 10 minutes Ready for WG last call? Anycast Address Assignment using DHCPv6 Syam Madanapalli 10 minutes Accept as dhc WG work item? Source Address Selection Policy option for DHCPv6 T. Fujisaki 10 minutes (available as http://www.nttv6.net/~arifumi/draft-hirotaka-dhc-source-address-selection-opt-00.txt) Accept as dhc WG work item? DHCPv6 Relay Agent Information Option Wing Cheong Lau 10 minutes Accept as dhc WG work item? DHCP-DNS interaction Bernie Volz 30 minutes Technical discussion ----------- 120 minutes _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Oct 29 05:25:49 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 FAA10982 for ; Fri, 29 Oct 2004 05:25:49 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNTFK-0001kw-Lw for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 05:40:35 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNSSJ-0005X8-Kv; Fri, 29 Oct 2004 04:49:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNSIO-0006te-W9 for dhcwg@megatron.ietf.org; Fri, 29 Oct 2004 04:39:41 -0400 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 EAA07982 for ; Fri, 29 Oct 2004 04:39:38 -0400 (EDT) Received: from goliath.siemens.de ([192.35.17.28]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNSWd-0000ri-4K for dhcwg@ietf.org; Fri, 29 Oct 2004 04:54:24 -0400 Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id i9T8daP6007881; Fri, 29 Oct 2004 10:39:36 +0200 Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99]) by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id i9T8daBO016475; Fri, 29 Oct 2004 10:39:36 +0200 Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72) id <4BVR70K6>; Fri, 29 Oct 2004 10:39:36 +0200 Message-ID: <2A8DB02E3018D411901B009027FD3A3F0468693F@mchp905a.mch.sbs.de> From: Tschofenig Hannes To: "'Ralph Droms'" , dhcwg@ietf.org Subject: RE: [dhcwg] IMPORTANT!!! dhc WG meeting now Tue AM Date: Fri, 29 Oct 2004 10:39:26 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 1.3 (+) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 1.3 (+) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 hi ralph, hi all, the dhc agenda raised my interest. i would like to know more about " DHCP Authentication via EAP Mark Stapp 10 minutes Technical discussion " ciao hannes > -----Original Message----- > From: Ralph Droms [mailto:rdroms@cisco.com] > Sent: Donnerstag, 28. Oktober 2004 17:33 > To: dhcwg@ietf.org > Subject: [dhcwg] IMPORTANT!!! dhc WG meeting now Tue AM > > Please be aware that, as of the most recent IETF 61 agenda > http://ietf.org/meetings/agenda_61.html (updated 10/27), the > dhc WG is now scheduled to meet: > > TUESDAY, November 9, 2004 > 0900-1130 Morning Sessions > INT dhc Dynamic Host Configuration WG * > RTG mpls Multiprotocol LabelSwitching WG > SEC btns Better-Than-Nothing Security BOF > SEC ltans Long-Term Archive and Notary Services WG > TSV ippm IP Performance Metrics WG > TSV sipping Session Initiation Protocol WG > > - Ralph > > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Oct 29 08:12:46 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 IAA22728 for ; Fri, 29 Oct 2004 08:12:46 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNVqu-0005Nm-Ae for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 08:27:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNVYf-0006kk-Fa; Fri, 29 Oct 2004 08:08:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNVGb-0006Kh-4I for dhcwg@megatron.ietf.org; Fri, 29 Oct 2004 07:50:01 -0400 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 HAA20979 for ; Fri, 29 Oct 2004 07:49:59 -0400 (EDT) Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNVUr-0004qg-FU for dhcwg@ietf.org; Fri, 29 Oct 2004 08:04:46 -0400 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-2.cisco.com with ESMTP; 29 Oct 2004 07:49:30 -0400 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9TBnRps011102; Fri, 29 Oct 2004 07:49:27 -0400 (EDT) Received: from rdroms-w2k01.cisco.com (sjc-vpn1-176.cisco.com [10.21.96.176]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMQ71835; Fri, 29 Oct 2004 07:49:24 -0400 (EDT) Message-Id: <4.3.2.7.2.20041029063111.02852d20@flask.cisco.com> X-Sender: rdroms@flask.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 29 Oct 2004 07:49:21 -0400 To: "Kuntal Chowdhury" From: Ralph Droms Subject: RE: [dhcwg] BCMCS server option drafts In-Reply-To: <591B780D9676844E8A704B5B013FFE920387C3BD@zrc2hxm1.corp.nor tel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 6b519fb0ef66258f34533f52ff46aedf Cc: dhcwg@ietf.org, Bernie Volz X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 79bb66f827e54e9d5c5c7f1f9d645608 Kuntal - in both DHCPv4 and DHCPv6, there are no required semantic ties between the message from the client to the server and the response from the server. That is, the client is not required to include any option request information or vendor identification (I'm using general terms rather than specific options because of the differences between DHCPv4 and DHCPv6) to cause the server to send certain options or vendor-specific information back to the client. The server uses any option request information or vendor identification or vendor-specific information as input ("hints") to the rules the server uses to send a response to the client. The server is free to send information that has not been specifically requested by the client, based on other information the server gleans from the message it receives from the client. So, in the DHCPv6 case, the client is not required to send an OPTION_ORO requesting OPTION_VENDOR_OPTS (although it may do so) and the server, based on other information, is free to send OPTION_VENDOR_OPTS. In a 3GPP2 deployment, if the DHCPv6 server sees a request from a part of the network topology known to be using 3GPP2, the server may assume that the device sending the request is a 3GPP2 device and send 3GPP2 OPTION_VENDOR_OPTS to that client. And, if, for some reason, the client is not a 3GPP2 device, the client can simply ignore the 3GPP2 OPTION_VENDOR_OPTS. The 3GPP2 standards bodies are free to define any syntax or semantics for the 3GPP2 OPTION_VENDOR_OPTS. So, if 3GPP2 coule require that a client sends a 3GPP2 OPTION_VENDOR_OPTS request, which the server parses and responds with 3GPP2 OPTION_VENDOR_OPTS containing information for the client. - Ralph At 03:08 PM 10/28/2004 -0400, Kuntal Chowdhury wrote: >Hello Bernie, > >Thanks for the response. I guess what is not clear to me is how a DHCP >client requests vendor specific information from the DHCP server: > >" >- A Client includes OPTION_VENDOR_CLASS to identify itself. >- A Client MAY include OPTION_VENDOR_OPTS if it has vendor specific data >(other than classing information) to communicate. >- A Server includes OPTION_VENDOR_OPTS for matching enterprise IDs (and >class data, if appropriate). This is only REQUIRED if the ORO includes the >OPTION_VENDOR_OPTS code (the ORO doesn't say which vendors; that is handled >by OPTION_VENDOR_CLASS). >" > >Second bullet seems to say that the DHCP client includes OPTION_VENDOR_OPTS >to convey some vendor specific information to the DHCP server beside the >vendor class info (which is in OPTION_VENDOR_CLASS). It does not state that >OPTION_VENDOR_OPTS is included in a DHCP message (such as information >request) to REQUEST for vendor specific info from the server. It is true >that opcode for OPTION_VENDOR_OPTS can be included in ORO, but that won't >necessarily indicate to the server which vendor specific codes it needs to >return to the client. Also, the format of the OPTION_VENDOR_OPTS when it >appears in the REQUEST message is unclear. > >A clear description of how to use OPTION_VENDOR_OPTS to request vendor >specific information (such as broadcast server address) will be required by >SDOs such as 3GPP2. > >Regards, >Kuntal > > > >-----Original Message----- > >From: Bernie Volz [mailto:volz@cisco.com] > >Sent: Wednesday, October 27, 2004 8:34 PM > >To: Chowdhury, Kuntal [RICH1:2H18:EXCH]; 'Ralph Droms' > >Cc: dhcwg@ietf.org > >Subject: RE: [dhcwg] BCMCS server option drafts > > > > > >Hi: > > > >I believe the original model was for OPTION_VENDOR_CLASS to be > >similar to DHCPv4 Vendor class identifier option (option 60) > >and for OPTION_VENDOR_OPTS to be similar to DHCPv4 Vendor > >Specific Information (option 43). > > > >You might refer to draft-ietf-dhc-vendor-03.txt, while for > >DHCPv4, it does have some additional information about how the > >options might be used. That work is modeled on the DHCPv6 > >options. In particular, see section 4: > > > >4. Vendor-Identifying Vendor-Specific Information Option > > > > DHCP clients and servers may use this option to exchange vendor- > > specific information. Either party may send this option, as needed. > > While a typical case might be for a client to send the > > Vendor-Identifying Vendor Class option, to elicit a useful > > Vendor-Identifying Vendor-Specific Information Option, there is no > > requirement for such a flow. > > > >It would be good to get general agreement on this as you're > >perhaps the first user. And, it would be best to set a > >"standard" for others to follow. > > > >I kind of liked the DHCPv4 model, as it is much easier and > >clearly to understand (and implement for clients and servers): > >- A Client includes OPTION_VENDOR_CLASS to identify itself. > >- A Client MAY include OPTION_VENDOR_OPTS if it has vendor > >specific data (other than classing information) to communicate. > >- A Server includes OPTION_VENDOR_OPTS for matching enterprise > >IDs (and class data, if appropriate). This is only REQUIRED if > >the ORO includes the OPTION_VENDOR_OPTS code (the ORO doesn't > >say which vendors; that is handled by OPTION_VENDOR_CLASS). > >- I'm not sure why a server would ever need to include > >OPTION_VENDOR_CLASS, though perhaps it could tell the client > >what implementation the server is so that perhaps the client > >knows it could use some extended capabilities? Or, the server > >could send back whatever the client sent to it? > > > >But, as draft-ietf-dhc-vendor-03.tx states, this is not the > >only possible model. > > > >Note that in your case, I would assume that the > >OPTION_VENDOR_CLASS would have your enterprise ID and some > >class information to indicate what capabilities the client > >supports (and therefore the server should provide > >configuration for in the OPTION_VENDOR_OPTS). > > > >So, this is a good issue for the DHC WG to resolve and clarify > >for a future RFC 3315bis. > > > >- Bernie > > > >> -----Original Message----- > >> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] > >> On Behalf Of Kuntal Chowdhury > >> Sent: Wednesday, October 27, 2004 4:33 PM > >> To: Ralph Droms; volz@cisco.com > >> Cc: dhcwg@ietf.org > >> Subject: RE: [dhcwg] BCMCS server option drafts > >> > >> > >> I have a few questions on the possible use of DHCPv6 > >> OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS to request vendor > >> specific info: > >> > >> 1. Since the enterprise number is included in > >> OPTION_VENDOR_OPTS, will it suffice to use only this option > >> in the information request message from the DHCP client? Is > >> the use of OPTION_VENDOR_CLASS mandatory while vendor > >> specific options are requested? > >> > >> 2. Does the mere inclusion of OPTION_VENDOR_OPTS in the > >> information request message indicate to the DHCP server that > >> the DHCP client is requesting for some specific vendor > >> specific options? > >> > >> 3. O-R-O has the format where each of requested option codes > >> are listed in it. However, in OPTION_VENDOR_OPTS the > >> encapsulated vendor-specific options field MUST be encoded as > >> a sequence of code/length/value fields. What value does the > >> DHCP client use while requesting for a vendor specific option? > >> > >> These things are not clearly defined in RFC3315. > >> > >> Regards, > >> Kuntal > >> > >> >-----Original Message----- > >> >From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On > >> >Behalf Of Ralph Droms > >> >Sent: Wednesday, October 27, 2004 2:29 PM > >> >To: dhcwg@ietf.org > >> >Subject: RE: [dhcwg] BCMCS server option drafts > >> > > >> > > >> > > >> >What about the deployment issue? The 3GGP2 specification will be > >> >ratified in November, with deployment following soon. Some service > >> >providers already have DHCP servers in place that must be > >updated for > >> >any new options. The options defined in the current drafts can > >> >likely be supported without code changes to existing servers, > >> >allowing for faster deployment. Use of a VIVSO sub-option would > >> >require code changes to existing servers. How long would > >it take to > >> >deploy DHCP server that can support VIVSO? > >> > > >> >BTW, we need more discussion of this issue *soon* due to the time > >> >constraints of the upcoming 3GPP2 standards process and deployment. > >> > > >> >- Ralph > >> > > >> >At 04:12 PM 10/21/2004 -0400, Bernie Volz wrote: > >> >>Personally, I'd like to see the DHCPv4 VIVSO get deployed > >> and pushing > >> >>these options to using it would be a step at making this > >> >happen (as one > >> >>would expect 3GPP2 vendors to have some significant input to the > >> >>decisions of DHCP server vendors). > >> >> > >> >>It also means that 3GPP2 is free to define other VIVSO > >> options in the > >> >>future within their own forum and need not go to the IETF > >> >(and DHC WG). > >> >>I suspect that this would provide much faster deployment > >for them in > >> >>the future. > >> >> > >> >>Also, the DHCPv6 OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS > >> >are already > >> >>there for DHCPv6. > >> >> > >> >>BTW, 3GPP2 already has an enterprise-id number: > >> >> > >> >>5535 > >> >> 3rd Generation Partnership Project 2 (3GPP2) > >> >> Allen Long > >> >> along@cisco.com > >> >> > >> >>So, they'd be good to go! > >> >> > >> >>- Bernie > >> >> > >> >> > -----Original Message----- > >> >> > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On > >> >> > Behalf Of Ralph Droms > >> >> > Sent: Thursday, October 21, 2004 2:35 PM > >> >> > To: dhcwg@ietf.org > >> >> > Subject: [dhcwg] BCMCS server option drafts > >> >> > > >> >> > > >> >> > We need to have a short WG conversation about two options > >> >that were > >> >> > discussed at the WG meeting in San Diego. The outcome of the > >> >> > conversation will be to determine consensus about taking > >> on these > >> >> > two > >> >> > drafts: > >> >> > > >> >> > draft-chowdhury-dhc-bcmcv4-option-01.txt > >> >> > draft-chowdhury-dhc-bcmcv6-option-01.txt > >> >> > > >> >> > as dhc WG work items or recommending that 3GPP2 define > >> >> > vendor-identifying vendor-specific option (VIVSO; option code > >> >> > 125) sub-options to carry the information described in > >> the drafts. > >> >> > > >> >> > If the WG consensus is to take on the drafts as WG work items > >> >> > drafts, are they acceptable as currently published? > >> >> > > >> >> > Because of the time constraints imposed by the 3GPP2 > >> schedule, I'm > >> >> > going to cut off discussion on this topic next Thursday, > >> >10/28, and > >> >> > determine WG consensus at that time. > >> >> > > >> >> > Here are some considerations for discussion: > >> >> > > >> >> > 3GPP2 has defined some vendor-specific sub-options, for > >> >example, to > >> >> > identify a MIP home agent for the DHCP client. > >> >> > > >> >> > A 3GPP2 client needs to specify to the DHCP server which > >> >parameters > >> >> > it needs - specifically, whether it needs to receive the BCMCS > >> >> > servers. If the current drafts are adopted, the client > >> can simply > >> >> > use the parameter request list option (option code 55) for the > >> >> > request. If a VIVSO sub-option is used, 3GPP2 would > >> also define a > >> >> > parameter request list sub-option. > >> >> > > >> >> > There is a deployment issue, as some service providers > >> >already have > >> >> > DHCP servers in place that must be updated for any new > >> >options. Is > >> >> > it the case that the options defined in the current > >drafts can be > >> >> > supported without code changes to existing servers? Use > >> >of a VIVSO > >> >> > sub-option would require code changes to existing servers. > >> > How long > >> >> > would it take to deploy DHCP server that can support VIVSO. > >> >> > > >> >> > BCMCS may be adopted across multiple technologies, so the > >> >options in > >> >> > the current drafts would not be specific to 3GPP2. > >However, the > >> >> > BCMCS specification has not adopted by other standards, > >> yet, so we > >> >> > may need to define additional options for related > >> services in the > >> >> > future if those services are not interoperable with the > >> >3GPP2 BCMCS > >> >> > service. > >> >> > > >> >> > CableLabs has one option with sub-options (RFC 3495) > >rather than > >> >> > multiple options because: > >> >> > * wanted to avoid exhaustion of DHCP option code space; > >> >perhaps less > >> >> > of an issue with option code reclassification > >> >> > * would have used VIVSO if available > >> >> > * use of VIVSO with sub-options would give 3GPP2 freedom > >> >to define new > >> >> > sub-options on demand > >> >> > Do these considerations have an impact on our decision > >> >about how to > >> >> > proceed with the 3GPP2 options? > >> >> > > >> >> > - Ralph > >> >> > > >> >> > > >> >> > _______________________________________________ > >> >> > dhcwg mailing list > >> >> > dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg > >> >> > > >> > > >> > > >> >_______________________________________________ > >> >dhcwg mailing list > >> >dhcwg@ietf.org > >> >https://www1.ietf.org/mailman/listinfo/dhcwg > >> > > >> > > >> > >> _______________________________________________ > >> dhcwg mailing list > >> dhcwg@ietf.org > >> https://www1.ietf.org/mailman/listinfo/dhcwg > >> > > > > > > > >_______________________________________________ >dhcwg mailing list >dhcwg@ietf.org >https://www1.ietf.org/mailman/listinfo/dhcwg _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Oct 29 13:07:03 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 NAA16116 for ; Fri, 29 Oct 2004 13:07:03 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNaRk-0003bX-Rl for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 13:21:54 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNa03-0006hs-B9; Fri, 29 Oct 2004 12:53:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNZrh-0000L9-Uy for dhcwg@megatron.ietf.org; Fri, 29 Oct 2004 12:44:38 -0400 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 MAA14275 for ; Fri, 29 Oct 2004 12:44:35 -0400 (EDT) Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNa61-00032c-4q for dhcwg@ietf.org; Fri, 29 Oct 2004 12:59:25 -0400 Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i9TGi0u24082 for ; Fri, 29 Oct 2004 12:44:00 -0400 (EDT) Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 29 Oct 2004 12:44:01 -0400 Message-ID: <591B780D9676844E8A704B5B013FFE92038DE042@zrc2hxm1.corp.nortel.com> From: "Kuntal Chowdhury" To: dhcwg@ietf.org Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option Date: Fri, 29 Oct 2004 12:43:48 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 A few questions on this draft: 1. The primary motivation seems to be 3GPP2's network, but fact of the matter is, 3GPP2 NAS (PDSN) does not push information received from a different domain into the DHCP server in the local domain. 2. The draft allows vendor specific RADIUS attributes to be pushed to the DHCP server potentially from different domains. How does the DHCP sever parse these vendor specific RADIUS attributes? Is it the assumption that the DHCP server needs to know possibly all vendor specific RADIUS attributes? This does not scale. 3. It says that the DHCP server uses this RADIUS info to do IP address allocation and other parameter allocation. It would be nice to know what other parameters the authors have in mind. Regards, Kuntal -----Original Message----- From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Wing Cheong Lau Sent: Monday, October 25, 2004 1:59 PM To: Bernie Volz; 'Wing Cheong Lau'; dhcwg@ietf.org Cc: Ted.Lemon@nominum.com; rdroms@cisco.com Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option At 10:11 AM 10/25/2004, Bernie Volz wrote: BTW, we don't need a DHCPv6 version of draft-ietf-dhc-vendor-suboption-00.txt because the existing DHCPv6 Vendor options can be used by the Relay Agent just fine. Again, it is WHERE these options appear that indicates whether they are for the client (in the client part of the message) or the relay, in the Relay-Forw or Relay-Reply part of the message. That work is already done and is not needed!! - Bernie I see. However, the use of such vendor-options by the Relay Agent is kind of hidden/missing from the current text of RFC 3315. For example, Sections 22.16 and 22.17 of RFC 3315 only describe the use of such vendor options by the client and the server. The use of these options by the relay agent are not mentioned at all. While it is true that the table in Appendix A of RFC3315 does say the possible inclusion of the vendor options in the Relay-Forward/Relay-Reply message, the table in Appendix B seems to imply otherwise: In the table in Appendix B, while there are "*"'s for the Relay-Message and Interface ID rows under the Relay Forw./Relay Replay columns, no "*"'s are found for the Vendor Class/Vendor Info rows for the Relay Forw./Relay Replay columns. I think if Relay agent is allowed to include those vendor options in the Relay Forw/Replay messages, just like it includes the Interface option, the rows for the Vendor options should look like the row of the Interface option. Am I missing something ? or did I misunderstand the entire meaning of the table in Appendix B ? Actually, what does the "Option Field" column in the table mean ? Also what's the "Note" below the table refers to ? Would you share more clarification/ insights on this ? Thanks a lot in advance. Regards, Wing _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Oct 29 14:48:12 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 OAA23323 for ; Fri, 29 Oct 2004 14:48:12 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNc1d-0005jg-AV for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 15:03:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNbkm-0007zu-2s; Fri, 29 Oct 2004 14:45:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNbeF-0003lI-0i for dhcwg@megatron.ietf.org; Fri, 29 Oct 2004 14:38:51 -0400 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 OAA22547 for ; Fri, 29 Oct 2004 14:38:49 -0400 (EDT) Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNbsY-0005Sj-MT for dhcwg@ietf.org; Fri, 29 Oct 2004 14:53:39 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9TIcFeD015573; Fri, 29 Oct 2004 11:38:15 -0700 (PDT) Received: from WLAU.qualcomm.com (wlau.qualcomm.com [129.46.74.167]) by neophyte.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9TIcC9A024839; Fri, 29 Oct 2004 11:38:13 -0700 (PDT) Message-Id: <6.0.0.22.2.20041029110145.0480ccf0@qcmail1.qualcomm.com> X-Sender: wlau@qcmail1.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 29 Oct 2004 11:38:12 -0700 To: "Kuntal Chowdhury" From: Wing Cheong Lau Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option In-Reply-To: <591B780D9676844E8A704B5B013FFE92038DE042@zrc2hxm1.corp.nor tel.com> References: <591B780D9676844E8A704B5B013FFE92038DE042@zrc2hxm1.corp.nortel.com> Mime-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0609649224==" Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f2728948111f2edaaf8980b5b9de55af --===============0609649224== Content-Type: multipart/alternative; boundary="=====================_479509037==.ALT" --=====================_479509037==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed At 09:43 AM 10/29/2004, you wrote: >A few questions on this draft: > >1. The primary motivation seems to be 3GPP2's network, but fact of the >matter is, 3GPP2 NAS (PDSN) does not push information received from a >different domain into the DHCP server in the local domain. Yes. That is the status quo. But the intent of the internet draft is to keep the possibility of such protocol support for roaming mobile scenario in the future. Of course, as clearly stated in the current draft regarding it's applicability and security implication need to be considered. In particular: "The scope of applicability of this specification is such that the NAS (which acts as a DHCP relay agent), any other participating DHCP relay agent, the DHCP server and DHCP client should be within the same administrative domain while the RADIUS service involved may span multiple administrative domains. See the Section 5 for details of security considerations when this specification is deployed with RADIUS service operating across multiple administrative domains. Global interoperability of this specification, across arbitrary administrative domains, is not supported. " and "The RADIUS protocol [6] was designed for intra-domain use, where the NAS, proxy, and home server exist within a single administrative domain, and proxies may be considered a trusted component. However, under roaming situation, the NAS, proxies, and home server will typically be managed by different administrative entities. As a result, inter-domain RADIUS operations are inherently required for roaming applications, and proxies cannot necessarily be trusted. Refer to Section 7 of RFC 2609 for a detailed security threat analysis, limitations and precautions of operating RADIUS in a inter- domain environment. In general, robust and secure operations of RADIUS across multiple administrative domains require pre-established agreement, mutual trust, and secure communications channel amongst all the participating domains." Inter-domain RADIUS operations have its well-known set of risks and limitations and any future applications of the proposed options in an cross-domain environment would be subjected to such considerations. >2. The draft allows vendor specific RADIUS attributes to be pushed to the >DHCP server potentially from different domains. How does the DHCP sever >parse these vendor specific RADIUS attributes? Is it the assumption that the >DHCP server needs to know possibly all vendor specific RADIUS attributes? >This does not scale. In general, as specified in the draft, the DHCP server "MAY" use the information carried in the proposed option as a HINT to make the subsequent assignment. If the DHCP server does not understand a particular vendor-specific option/VSA, it is free to ignore it when making its assignment. On the other hand, given a specific deployment environment, it is not unreasonable to assume the DHCP server would understand a particular set of vendor-specific, e.g. 3GPP2, RADIUS VSA's. After all, as stated in the applicability statement above, we are not talking about cross-domain RADIUS services over any arbitrary domain, but only over those which have some sort of pre-established roaming agreements. >3. It says that the DHCP server uses this RADIUS info to do IP address >allocation and other parameter allocation. It would be nice to know what >other parameters the authors have in mind. > >Regards, >Kuntal Parameters under considerations included Home Agent address, (for dynamic HA assignment), Home Address (HoA) and/or Home-link prefix, etc. In fact, my understanding is that, for a single domain environment, RADIUS 3GPP2 VSA's have already been defined for these set of parameters to enable MIP6 bootstrapping via RADIUS/DHCPv6 within a single domain. If the risks/limitations of cross-domain RADIUS service stated above are deemed to be acceptable, there is a possibility that such bootstrapping scheme can be extended across providers with pre-established roaming agreements. Regards, Wing --=====================_479509037==.ALT Content-Type: text/html; charset="us-ascii" At 09:43 AM 10/29/2004, you wrote:
A few questions on this draft:

1. The primary motivation seems to be 3GPP2's network, but fact of the
matter is, 3GPP2 NAS (PDSN) does not push information received from a
different domain into the DHCP server in the local domain.

Yes. That is the status quo. But the intent of the internet draft is to keep
the possibility of such protocol support for roaming mobile scenario in the future. 
Of course, as clearly stated in the current draft regarding it's applicability and
security implication need to be considered. In particular:

"The scope of applicability of this specification is such that the NAS
   (which acts as a DHCP relay agent), any other participating DHCP
   relay agent, the DHCP server and DHCP client should be within the
   same administrative domain while the RADIUS service involved may span
   multiple administrative domains. See the Section 5 for details of
   security considerations when this specification is deployed with
   RADIUS service operating across multiple administrative domains.
   Global interoperability of this specification, across arbitrary
   administrative domains, is not supported. "

and

"The RADIUS protocol [6] was designed for intra-domain use, where the
   NAS, proxy, and home server exist within a single administrative
   domain, and proxies may be considered a trusted component. However,
   under roaming situation, the NAS, proxies, and home server will
   typically be managed by different administrative entities. As a
   result, inter-domain RADIUS operations are inherently required for
   roaming applications, and proxies cannot necessarily be trusted. 
   Refer to Section 7 of RFC 2609 for a detailed security threat
   analysis, limitations and precautions of operating RADIUS in a inter-
   domain environment. In general, robust and secure operations of
   RADIUS across multiple administrative domains require pre-established
   agreement, mutual trust, and secure communications channel amongst
   all the participating domains."

Inter-domain RADIUS operations have its well-known
set of risks and limitations and any future applications of the proposed options
in an cross-domain environment would be subjected to such considerations. 



2. The draft allows vendor specific RADIUS attributes to be pushed to the
DHCP server potentially from different domains. How does the DHCP sever
parse these vendor specific RADIUS attributes? Is it the assumption that the
DHCP server needs to know possibly all vendor specific RADIUS attributes?
This does not scale.
In general, as specified in the draft, the DHCP server "MAY" use the information carried in the proposed option as a HINT to make the subsequent assignment. If  the DHCP server does not
understand a particular vendor-specific option/VSA, it is free to ignore it when making its
assignment. On the other hand, given a specific deployment environment, it is not unreasonable to
assume the DHCP server would understand a particular set of vendor-specific, e.g. 3GPP2, RADIUS VSA's. After all, as stated in the applicability statement above, we are not talking about cross-domain RADIUS services over any arbitrary domain, but only over those which have some sort of pre-established roaming agreements.


3. It says that the DHCP server uses this RADIUS info to do IP address
allocation and other parameter allocation. It would be nice to know what
other parameters the authors have in mind.

Regards,
Kuntal
Parameters under considerations included Home Agent address, (for dynamic HA assignment),
Home Address (HoA) and/or Home-link prefix, etc.

In fact, my understanding is that, for a single
domain environment, RADIUS 3GPP2 VSA's have already been defined for these set of
parameters to enable MIP6 bootstrapping  via RADIUS/DHCPv6 within a single domain.
 
If the risks/limitations of cross-domain RADIUS service stated above  are deemed to be acceptable,
there is a possibility that such bootstrapping scheme can be extended across providers with
pre-established roaming agreements.

Regards,

Wing --=====================_479509037==.ALT-- --===============0609649224== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --===============0609649224==-- From dhcwg-bounces@ietf.org Fri Oct 29 14:59:24 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 OAA24118 for ; Fri, 29 Oct 2004 14:59:24 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNcCU-0005xO-5V for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 15:14:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNbl6-0008FL-5O; Fri, 29 Oct 2004 14:45:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNbjf-00077a-61 for dhcwg@megatron.ietf.org; Fri, 29 Oct 2004 14:44:27 -0400 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 OAA22932 for ; Fri, 29 Oct 2004 14:44:25 -0400 (EDT) Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNbxy-0005Zf-QJ for dhcwg@ietf.org; Fri, 29 Oct 2004 14:59:15 -0400 Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i9TIhq915946; Fri, 29 Oct 2004 14:43:52 -0400 (EDT) Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 29 Oct 2004 14:43:53 -0400 Message-ID: <591B780D9676844E8A704B5B013FFE92038DE221@zrc2hxm1.corp.nortel.com> From: "Kuntal Chowdhury" To: Ralph Droms Subject: RE: [dhcwg] BCMCS server option drafts Date: Fri, 29 Oct 2004 14:43:37 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 14278aea5bdd1edf35ec09ffb7b61f9d Cc: dhcwg@ietf.org, Bernie Volz X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 00134749b78ab2213964fc53d03de937 Hello Ralph, >The 3GPP2 standards bodies are free to define any syntax or >semantics for the 3GPP2 OPTION_VENDOR_OPTS. So, if 3GPP2 >coule require that a client sends a 3GPP2 OPTION_VENDOR_OPTS >request, which the server parses and responds with 3GPP2 >OPTION_VENDOR_OPTS containing information for the client. If I understand what your are saying, the semantics to request/respond vendor specific information should also be vendor specific. I guess this is well understood to the DHCP implementers. It was not clear to me when I read RFC 3115. The syntax of OPTION_VENDOR_OPTS is defined in 3315: " The encapsulated vendor-specific options field MUST be encoded as a sequence of code/length/value fields of identical format to the DHCP options field. The option codes are defined by the vendor identified in the enterprise-number field and are not managed by IANA. Each of the encapsulated options is formatted as follows: 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | opt-code | option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . . option-data . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ " So, I don't understand your statement "3GPP2 is free to define the syntax of OPTION_VENDOR_OPTS". The syntax of OPTION_VENDOR_OPTS when it appears in a request message from the client is not clear. The suggested behavior of a 3GPP2 DHCP server sending all 3GPP2 specific information to the client (blindly) is not an ideal one. The approach where the client sends specific information request and the server returns the requested information only is a better one, IMHO. -Kuntal >-----Original Message----- >From: Ralph Droms [mailto:rdroms@cisco.com] >Sent: Friday, October 29, 2004 6:49 AM >To: Chowdhury, Kuntal [RICH1:2H18:EXCH] >Cc: Bernie Volz; dhcwg@ietf.org >Subject: RE: [dhcwg] BCMCS server option drafts > > >Kuntal - in both DHCPv4 and DHCPv6, there are no required >semantic ties between the message from the client to the >server and the response from the server. That is, the client >is not required to include any option request information or >vendor identification (I'm using general terms rather than >specific options because of the differences between DHCPv4 and >DHCPv6) to cause the server to send certain options or >vendor-specific information back to the client. The server >uses any option request information or vendor identification >or vendor-specific information as input ("hints") to the rules >the server uses to send a response to the client. The server >is free to send information that has not been specifically >requested by the client, based on other information the server >gleans from the message it receives from the client. > >So, in the DHCPv6 case, the client is not required to send an >OPTION_ORO requesting OPTION_VENDOR_OPTS (although it may do >so) and the server, based on other information, is free to >send OPTION_VENDOR_OPTS. In a 3GPP2 deployment, if the DHCPv6 >server sees a request from a part of the network topology >known to be using 3GPP2, the server may assume that the device >sending the request is a 3GPP2 device and send 3GPP2 >OPTION_VENDOR_OPTS to that client. And, if, for some reason, >the client is not a 3GPP2 device, the client can simply ignore >the 3GPP2 OPTION_VENDOR_OPTS. > >The 3GPP2 standards bodies are free to define any syntax or >semantics for the 3GPP2 OPTION_VENDOR_OPTS. So, if 3GPP2 >coule require that a client sends a 3GPP2 OPTION_VENDOR_OPTS >request, which the server parses and responds with 3GPP2 >OPTION_VENDOR_OPTS containing information for the client. > > >- Ralph > > >At 03:08 PM 10/28/2004 -0400, Kuntal Chowdhury wrote: >>Hello Bernie, >> >>Thanks for the response. I guess what is not clear to me is >how a DHCP >>client requests vendor specific information from the DHCP server: >> >>" >>- A Client includes OPTION_VENDOR_CLASS to identify itself. >>- A Client MAY include OPTION_VENDOR_OPTS if it has vendor specific >>data (other than classing information) to communicate. >>- A Server includes OPTION_VENDOR_OPTS for matching >enterprise IDs (and >>class data, if appropriate). This is only REQUIRED if the ORO >includes >>the OPTION_VENDOR_OPTS code (the ORO doesn't say which >vendors; that is >>handled by OPTION_VENDOR_CLASS). " >> >>Second bullet seems to say that the DHCP client includes >>OPTION_VENDOR_OPTS to convey some vendor specific information to the >>DHCP server beside the vendor class info (which is in >>OPTION_VENDOR_CLASS). It does not state that OPTION_VENDOR_OPTS is >>included in a DHCP message (such as information >>request) to REQUEST for vendor specific info from the server. >It is true >>that opcode for OPTION_VENDOR_OPTS can be included in ORO, >but that won't >>necessarily indicate to the server which vendor specific >codes it needs to >>return to the client. Also, the format of the >OPTION_VENDOR_OPTS when it >>appears in the REQUEST message is unclear. >> >>A clear description of how to use OPTION_VENDOR_OPTS to >request vendor >>specific information (such as broadcast server address) will be >>required by SDOs such as 3GPP2. >> >>Regards, >>Kuntal >> >> >> >-----Original Message----- >> >From: Bernie Volz [mailto:volz@cisco.com] >> >Sent: Wednesday, October 27, 2004 8:34 PM >> >To: Chowdhury, Kuntal [RICH1:2H18:EXCH]; 'Ralph Droms' >> >Cc: dhcwg@ietf.org >> >Subject: RE: [dhcwg] BCMCS server option drafts >> > >> > >> >Hi: >> > >> >I believe the original model was for OPTION_VENDOR_CLASS to be >> >similar to DHCPv4 Vendor class identifier option (option >60) and for >> >OPTION_VENDOR_OPTS to be similar to DHCPv4 Vendor Specific >> >Information (option 43). >> > >> >You might refer to draft-ietf-dhc-vendor-03.txt, while for >DHCPv4, it >> >does have some additional information about how the options >might be >> >used. That work is modeled on the DHCPv6 options. In >particular, see >> >section 4: >> > >> >4. Vendor-Identifying Vendor-Specific Information Option >> > >> > DHCP clients and servers may use this option to exchange vendor- >> > specific information. Either party may send this >option, as needed. >> > While a typical case might be for a client to send the >> > Vendor-Identifying Vendor Class option, to elicit a useful >> > Vendor-Identifying Vendor-Specific Information Option, >there is no >> > requirement for such a flow. >> > >> >It would be good to get general agreement on this as you're perhaps >> >the first user. And, it would be best to set a "standard" >for others >> >to follow. >> > >> >I kind of liked the DHCPv4 model, as it is much easier and >clearly to >> >understand (and implement for clients and servers): >> >- A Client includes OPTION_VENDOR_CLASS to identify itself. >> >- A Client MAY include OPTION_VENDOR_OPTS if it has vendor specific >> >data (other than classing information) to communicate. >> >- A Server includes OPTION_VENDOR_OPTS for matching enterprise IDs >> >(and class data, if appropriate). This is only REQUIRED if the ORO >> >includes the OPTION_VENDOR_OPTS code (the ORO doesn't say which >> >vendors; that is handled by OPTION_VENDOR_CLASS). >> >- I'm not sure why a server would ever need to include >> >OPTION_VENDOR_CLASS, though perhaps it could tell the client what >> >implementation the server is so that perhaps the client knows it >> >could use some extended capabilities? Or, the server could >send back >> >whatever the client sent to it? >> > >> >But, as draft-ietf-dhc-vendor-03.tx states, this is not the only >> >possible model. >> > >> >Note that in your case, I would assume that the OPTION_VENDOR_CLASS >> >would have your enterprise ID and some class information to >indicate >> >what capabilities the client supports (and therefore the server >> >should provide configuration for in the OPTION_VENDOR_OPTS). >> > >> >So, this is a good issue for the DHC WG to resolve and >clarify for a >> >future RFC 3315bis. >> > >> >- Bernie >> > >> >> -----Original Message----- >> >> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On >> >> Behalf Of Kuntal Chowdhury >> >> Sent: Wednesday, October 27, 2004 4:33 PM >> >> To: Ralph Droms; volz@cisco.com >> >> Cc: dhcwg@ietf.org >> >> Subject: RE: [dhcwg] BCMCS server option drafts >> >> >> >> >> >> I have a few questions on the possible use of DHCPv6 >> >> OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS to request vendor >> >> specific info: >> >> >> >> 1. Since the enterprise number is included in OPTION_VENDOR_OPTS, >> >> will it suffice to use only this option in the >information request >> >> message from the DHCP client? Is the use of OPTION_VENDOR_CLASS >> >> mandatory while vendor specific options are requested? >> >> >> >> 2. Does the mere inclusion of OPTION_VENDOR_OPTS in the >information >> >> request message indicate to the DHCP server that the DHCP >client is >> >> requesting for some specific vendor specific options? >> >> >> >> 3. O-R-O has the format where each of requested option codes are >> >> listed in it. However, in OPTION_VENDOR_OPTS the encapsulated >> >> vendor-specific options field MUST be encoded as a sequence of >> >> code/length/value fields. What value does the DHCP client >use while >> >> requesting for a vendor specific option? >> >> >> >> These things are not clearly defined in RFC3315. >> >> >> >> Regards, >> >> Kuntal >> >> >> >> >-----Original Message----- >> >> >From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On >> >> >Behalf Of Ralph Droms >> >> >Sent: Wednesday, October 27, 2004 2:29 PM >> >> >To: dhcwg@ietf.org >> >> >Subject: RE: [dhcwg] BCMCS server option drafts >> >> > >> >> > >> >> > >> >> >What about the deployment issue? The 3GGP2 specification will be >> >> >ratified in November, with deployment following soon. Some >> >> >service providers already have DHCP servers in place that must be >> >updated for >> >> >any new options. The options defined in the current drafts can >> >> >likely be supported without code changes to existing servers, >> >> >allowing for faster deployment. Use of a VIVSO sub-option would >> >> >require code changes to existing servers. How long would >> >it take to >> >> >deploy DHCP server that can support VIVSO? >> >> > >> >> >BTW, we need more discussion of this issue *soon* due to >the time >> >> >constraints of the upcoming 3GPP2 standards process and >> >> >deployment. >> >> > >> >> >- Ralph >> >> > >> >> >At 04:12 PM 10/21/2004 -0400, Bernie Volz wrote: >> >> >>Personally, I'd like to see the DHCPv4 VIVSO get deployed >> >> and pushing >> >> >>these options to using it would be a step at making this >> >> >happen (as one >> >> >>would expect 3GPP2 vendors to have some significant >input to the >> >> >>decisions of DHCP server vendors). >> >> >> >> >> >>It also means that 3GPP2 is free to define other VIVSO >> >> options in the >> >> >>future within their own forum and need not go to the IETF >> >> >(and DHC WG). >> >> >>I suspect that this would provide much faster deployment >> >for them in >> >> >>the future. >> >> >> >> >> >>Also, the DHCPv6 OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS >> >> >are already >> >> >>there for DHCPv6. >> >> >> >> >> >>BTW, 3GPP2 already has an enterprise-id number: >> >> >> >> >> >>5535 >> >> >> 3rd Generation Partnership Project 2 (3GPP2) >> >> >> Allen Long >> >> >> along@cisco.com >> >> >> >> >> >>So, they'd be good to go! >> >> >> >> >> >>- Bernie >> >> >> >> >> >> > -----Original Message----- >> >> >> > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] >> >> >> > On Behalf Of Ralph Droms >> >> >> > Sent: Thursday, October 21, 2004 2:35 PM >> >> >> > To: dhcwg@ietf.org >> >> >> > Subject: [dhcwg] BCMCS server option drafts >> >> >> > >> >> >> > >> >> >> > We need to have a short WG conversation about two options >> >> >that were >> >> >> > discussed at the WG meeting in San Diego. The >outcome of the >> >> >> > conversation will be to determine consensus about taking >> >> on these >> >> >> > two >> >> >> > drafts: >> >> >> > >> >> >> > draft-chowdhury-dhc-bcmcv4-option-01.txt >> >> >> > draft-chowdhury-dhc-bcmcv6-option-01.txt >> >> >> > >> >> >> > as dhc WG work items or recommending that 3GPP2 define >> >> >> > vendor-identifying vendor-specific option (VIVSO; option code >> >> >> > 125) sub-options to carry the information described in >> >> the drafts. >> >> >> > >> >> >> > If the WG consensus is to take on the drafts as WG >work items >> >> >> > drafts, are they acceptable as currently published? >> >> >> > >> >> >> > Because of the time constraints imposed by the 3GPP2 >> >> schedule, I'm >> >> >> > going to cut off discussion on this topic next Thursday, >> >> >10/28, and >> >> >> > determine WG consensus at that time. >> >> >> > >> >> >> > Here are some considerations for discussion: >> >> >> > >> >> >> > 3GPP2 has defined some vendor-specific sub-options, for >> >> >example, to >> >> >> > identify a MIP home agent for the DHCP client. >> >> >> > >> >> >> > A 3GPP2 client needs to specify to the DHCP server which >> >> >parameters >> >> >> > it needs - specifically, whether it needs to receive >the BCMCS >> >> >> > servers. If the current drafts are adopted, the client >> >> can simply >> >> >> > use the parameter request list option (option code >55) for the >> >> >> > request. If a VIVSO sub-option is used, 3GPP2 would >> >> also define a >> >> >> > parameter request list sub-option. >> >> >> > >> >> >> > There is a deployment issue, as some service providers >> >> >already have >> >> >> > DHCP servers in place that must be updated for any new >> >> >options. Is >> >> >> > it the case that the options defined in the current >> >drafts can be >> >> >> > supported without code changes to existing servers? Use >> >> >of a VIVSO >> >> >> > sub-option would require code changes to existing servers. >> >> > How long >> >> >> > would it take to deploy DHCP server that can support VIVSO. >> >> >> > >> >> >> > BCMCS may be adopted across multiple technologies, so the >> >> >options in >> >> >> > the current drafts would not be specific to 3GPP2. >> >However, the >> >> >> > BCMCS specification has not adopted by other standards, >> >> yet, so we >> >> >> > may need to define additional options for related >> >> services in the >> >> >> > future if those services are not interoperable with the >> >> >3GPP2 BCMCS >> >> >> > service. >> >> >> > >> >> >> > CableLabs has one option with sub-options (RFC 3495) >> >rather than >> >> >> > multiple options because: >> >> >> > * wanted to avoid exhaustion of DHCP option code space; >> >> >perhaps less >> >> >> > of an issue with option code reclassification >> >> >> > * would have used VIVSO if available >> >> >> > * use of VIVSO with sub-options would give 3GPP2 freedom >> >> >to define new >> >> >> > sub-options on demand >> >> >> > Do these considerations have an impact on our decision >> >> >about how to >> >> >> > proceed with the 3GPP2 options? >> >> >> > >> >> >> > - Ralph >> >> >> > >> >> >> > >> >> >> > _______________________________________________ >> >> >> > dhcwg mailing list >> >> >> > dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg >> >> >> > >> >> > >> >> > >> >> >_______________________________________________ >> >> >dhcwg mailing list >> >> >dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg >> >> > >> >> > >> >> >> >> _______________________________________________ >> >> dhcwg mailing list >> >> dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg >> >> >> > >> > >> > >> >>_______________________________________________ >>dhcwg mailing list >>dhcwg@ietf.org >>https://www1.ietf.org/mailman/listinfo/dhcwg > > > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Oct 29 15:24: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 PAA27885 for ; Fri, 29 Oct 2004 15:24:58 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNcbE-0006eR-TD for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 15:39:49 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNcLN-0007Wn-8b; Fri, 29 Oct 2004 15:23:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNc3p-0006Wc-MB for dhcwg@megatron.ietf.org; Fri, 29 Oct 2004 15:05:17 -0400 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 PAA24679 for ; Fri, 29 Oct 2004 15:05:15 -0400 (EDT) Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNcI8-00064e-Vk for dhcwg@ietf.org; Fri, 29 Oct 2004 15:20:06 -0400 Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i9TJ4bI24640 for ; Fri, 29 Oct 2004 15:04:38 -0400 (EDT) Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 29 Oct 2004 15:04:39 -0400 Message-ID: <591B780D9676844E8A704B5B013FFE92038DE296@zrc2hxm1.corp.nortel.com> From: "Kuntal Chowdhury" To: Wing Cheong Lau Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option Date: Fri, 29 Oct 2004 15:04:24 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b22590c27682ace61775ee7b453b40d3 I don't see the need for the following in the draft: 1. Reference to 3GPP2: because 3GPP2 does not use the scheme that you are proposing here. 2. Vendor specific attribute parsing requirement on the DHCP server: It does not scale. 3. The requirement of other parameter (non IP address) assignment by the DHCP server: because the examples you give viz. HA, HoA, Home Link prefix etc. are not something that the local domain (ASP) control as per MIP6. These are controlled by the Home/Serving MSP. -Kuntal -----Original Message----- From: Wing Cheong Lau [mailto:lau@qualcomm.com] Sent: Friday, October 29, 2004 1:38 PM To: Chowdhury, Kuntal [RICH1:2H18:EXCH] Cc: dhcwg@ietf.org Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option At 09:43 AM 10/29/2004, you wrote: A few questions on this draft: 1. The primary motivation seems to be 3GPP2's network, but fact of the matter is, 3GPP2 NAS (PDSN) does not push information received from a different domain into the DHCP server in the local domain. Yes. That is the status quo. But the intent of the internet draft is to keep the possibility of such protocol support for roaming mobile scenario in the future. Of course, as clearly stated in the current draft regarding it's applicability and security implication need to be considered. In particular: "The scope of applicability of this specification is such that the NAS (which acts as a DHCP relay agent), any other participating DHCP relay agent, the DHCP server and DHCP client should be within the same administrative domain while the RADIUS service involved may span multiple administrative domains. See the Section 5 for details of security considerations when this specification is deployed with RADIUS service operating across multiple administrative domains. Global interoperability of this specification, across arbitrary administrative domains, is not supported. " and "The RADIUS protocol [6] was designed for intra-domain use, where the NAS, proxy, and home server exist within a single administrative domain, and proxies may be considered a trusted component. However, under roaming situation, the NAS, proxies, and home server will typically be managed by different administrative entities. As a result, inter-domain RADIUS operations are inherently required for roaming applications, and proxies cannot necessarily be trusted. Refer to Section 7 of RFC 2609 for a detailed security threat analysis, limitations and precautions of operating RADIUS in a inter- domain environment. In general, robust and secure operations of RADIUS across multiple administrative domains require pre-established agreement, mutual trust, and secure communications channel amongst all the participating domains." Inter-domain RADIUS operations have its well-known set of risks and limitations and any future applications of the proposed options in an cross-domain environment would be subjected to such considerations. 2. The draft allows vendor specific RADIUS attributes to be pushed to the DHCP server potentially from different domains. How does the DHCP sever parse these vendor specific RADIUS attributes? Is it the assumption that the DHCP server needs to know possibly all vendor specific RADIUS attributes? This does not scale. In general, as specified in the draft, the DHCP server "MAY" use the information carried in the proposed option as a HINT to make the subsequent assignment. If the DHCP server does not understand a particular vendor-specific option/VSA, it is free to ignore it when making its assignment. On the other hand, given a specific deployment environment, it is not unreasonable to assume the DHCP server would understand a particular set of vendor-specific, e.g. 3GPP2, RADIUS VSA's. After all, as stated in the applicability statement above, we are not talking about cross-domain RADIUS services over any arbitrary domain, but only over those which have some sort of pre-established roaming agreements. 3. It says that the DHCP server uses this RADIUS info to do IP address allocation and other parameter allocation. It would be nice to know what other parameters the authors have in mind. Regards, Kuntal Parameters under considerations included Home Agent address, (for dynamic HA assignment), Home Address (HoA) and/or Home-link prefix, etc. In fact, my understanding is that, for a single domain environment, RADIUS 3GPP2 VSA's have already been defined for these set of parameters to enable MIP6 bootstrapping via RADIUS/DHCPv6 within a single domain. If the risks/limitations of cross-domain RADIUS service stated above are deemed to be acceptable, there is a possibility that such bootstrapping scheme can be extended across providers with pre-established roaming agreements. Regards, Wing _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From Spraguefaieo@nameplanet.com Fri Oct 29 16:32: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 QAA06398; Fri, 29 Oct 2004 16:32:28 -0400 (EDT) Received: from [61.215.96.156] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNdeZ-0000U4-G6; Fri, 29 Oct 2004 16:47:21 -0400 X-Message-Info: kxa45Tm532GccsGkaheOJTooOvkEZJ059 Received: from roland-dns.pcmail.com.tw ([105.60.232.72]) by b5-r809.pcmail.com.tw with Microsoft SMTPSVC(5.0.2195.6824); Fri, 29 Oct 2004 22:26:45 +0200 Date: Sat, 30 Oct 2004 00:24:45 +0400 (CST) Message-Id: <559212393.TYB151zlnRMfgk8206@rebecca63.teamwork38pcmail.com.tw> To: dhcwg-web-archive@ietf.org Subject: your husband needs to cope with the pain From: Abdul Sullivan MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--8-657439297-3415787038=:25763" X-Spam-Score: 16.0 (++++++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d ----8-657439297-3415787038=:25763 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable VIC0D1N
Pain Relief !
More info




enough



insensible jejuneholly kemp peaceableindigestion febrile wadsodden elfin lavoisierpearl chastity illegalbackplane bilinear clubperforce obtrusive doriacereal crewcut slewdutiable precede guidebremen ----8-657439297-3415787038=:25763-- From dhcwg-bounces@ietf.org Fri Oct 29 16:46:17 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 QAA09575 for ; Fri, 29 Oct 2004 16:46:17 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNdrx-0001Xh-G1 for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 17:01:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNcm1-0005Z1-RC; Fri, 29 Oct 2004 15:50:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNccB-0003wY-CM for dhcwg@megatron.ietf.org; Fri, 29 Oct 2004 15:40:47 -0400 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 PAA29240 for ; Fri, 29 Oct 2004 15:40:45 -0400 (EDT) Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNcqV-0006wd-I3 for dhcwg@ietf.org; Fri, 29 Oct 2004 15:55:36 -0400 Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-4.cisco.com with ESMTP; 29 Oct 2004 12:42:20 -0700 X-BrightmailFiltered: true Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i9TJeB81012220; Fri, 29 Oct 2004 12:40:12 -0700 (PDT) Received: from volzw2k (che-vpn-cluster-1-75.cisco.com [10.86.240.75]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AMR12342; Fri, 29 Oct 2004 15:40:09 -0400 (EDT) From: "Bernie Volz" To: "'Kuntal Chowdhury'" , "'Ralph Droms'" Subject: RE: [dhcwg] BCMCS server option drafts Date: Fri, 29 Oct 2004 15:40:09 -0400 Organization: Cisco Message-ID: <002f01c4bdef$19e70360$6701a8c0@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 In-Reply-To: <591B780D9676844E8A704B5B013FFE92038DE221@zrc2hxm1.corp.nortel.com> Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 08582f3b796126054df71137d5cb69f8 Content-Transfer-Encoding: quoted-printable Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c8d1e86bb8f49de8156b6392faa4a63b Content-Transfer-Encoding: quoted-printable I suspect Ralph meant that you're free to do whatever you want within = the bounds of the standard. This means you need to define 3GPP2 vendor = specific option codes, lengths, and contents. So, you might define the following 3GPP2 vendor-specific information = options that would be carried in the DHCPv6 OPTION_VENDOR_OPTS when the = enterprise ID is the 3GPP2 one: 1. 3GPP2_OPTION_ORO (=3D1). Same format as the ORO option, but carries = the 3GPP2 option numbers, not DHCPv6 ones. 2. 3GPP2_OPTION_BCMCS_SERVER_D (=3D2) (same format as in draft-chowdhury-dhc-bcmcv6-option-01.txt) 3. 3GPP2_OPTION_BCMCS_SERVER_A (=3D3) (same format as in draft-chowdhury-dhc-bcmcv6-option-01.txt) You can then have text that says "A server SHOULD return the 3GPP2 Vendor-Specific Options requested in the 3GPP2_OPTION_ORO option in a OPTION_VENDOR_OPTS with the 3GPP2 enterprise ID." A client would then send: OPTION_VENDOR_OPTS, length=3Dxx, data=3D<3ggp2 enterprise ID>, <3GPP2_OPTION_ORO>, , <3GPP2_OPTION_BCMCS_SERVER_D code>,<3GPP2_OPTION_BCMCS_SERVER_A code> The server would then respond with: OPTION_VENDOR_OPTS, length=3Dxx, data<3gpp2 enterprise ID>,=20 <3GPP2_OPTION_BCMCS_SERVER_D>, , <3GPP2_OPTION_BCMCS_SERVER_A>, , - Bernie > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20 > On Behalf Of Kuntal Chowdhury > Sent: Friday, October 29, 2004 2:44 PM > To: Ralph Droms > Cc: dhcwg@ietf.org; Bernie Volz > Subject: RE: [dhcwg] BCMCS server option drafts >=20 >=20 > Hello Ralph, >=20 > >The 3GPP2 standards bodies are free to define any syntax or > >semantics for the 3GPP2 OPTION_VENDOR_OPTS. So, if 3GPP2=20 > >coule require that a client sends a 3GPP2 OPTION_VENDOR_OPTS=20 > >request, which the server parses and responds with 3GPP2=20 > >OPTION_VENDOR_OPTS containing information for the client. >=20 > If I understand what your are saying, the semantics to=20 > request/respond vendor specific information should also be=20 > vendor specific. I guess this is well understood to the DHCP=20 > implementers. It was not clear to me when I read RFC 3115. >=20 > The syntax of OPTION_VENDOR_OPTS is defined in 3315: >=20 > " > The encapsulated vendor-specific options field MUST be encoded as a > sequence of code/length/value fields of identical format=20 > to the DHCP > options field. The option codes are defined by the vendor=20 > identified > in the enterprise-number field and are not managed by=20 > IANA. Each of > the encapsulated options is formatted as follows: >=20 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > =20 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | opt-code | =20 > option-len | > =20 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > . =20 > . > . option-data =20 > . > . =20 > . > =20 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > " >=20 > So, I don't understand your statement "3GPP2 is free to=20 > define the syntax of OPTION_VENDOR_OPTS". The syntax of=20 > OPTION_VENDOR_OPTS when it appears in a request message from=20 > the client is not clear.=20 >=20 > The suggested behavior of a 3GPP2 DHCP server sending all=20 > 3GPP2 specific information to the client (blindly) is not an=20 > ideal one. The approach where the client sends specific=20 > information request and the server returns the requested=20 > information only is a better one, IMHO. >=20 > -Kuntal >=20 > >-----Original Message----- > >From: Ralph Droms [mailto:rdroms@cisco.com] > >Sent: Friday, October 29, 2004 6:49 AM > >To: Chowdhury, Kuntal [RICH1:2H18:EXCH] > >Cc: Bernie Volz; dhcwg@ietf.org > >Subject: RE: [dhcwg] BCMCS server option drafts > > > > > >Kuntal - in both DHCPv4 and DHCPv6, there are no required > >semantic ties between the message from the client to the=20 > >server and the response from the server. That is, the client=20 > >is not required to include any option request information or=20 > >vendor identification (I'm using general terms rather than=20 > >specific options because of the differences between DHCPv4 and=20 > >DHCPv6) to cause the server to send certain options or=20 > >vendor-specific information back to the client. The server=20 > >uses any option request information or vendor identification=20 > >or vendor-specific information as input ("hints") to the rules=20 > >the server uses to send a response to the client. The server=20 > >is free to send information that has not been specifically=20 > >requested by the client, based on other information the server=20 > >gleans from the message it receives from the client. > > > >So, in the DHCPv6 case, the client is not required to send an > >OPTION_ORO requesting OPTION_VENDOR_OPTS (although it may do=20 > >so) and the server, based on other information, is free to=20 > >send OPTION_VENDOR_OPTS. In a 3GPP2 deployment, if the DHCPv6=20 > >server sees a request from a part of the network topology=20 > >known to be using 3GPP2, the server may assume that the device=20 > >sending the request is a 3GPP2 device and send 3GPP2=20 > >OPTION_VENDOR_OPTS to that client. And, if, for some reason,=20 > >the client is not a 3GPP2 device, the client can simply ignore=20 > >the 3GPP2 OPTION_VENDOR_OPTS. > > > >The 3GPP2 standards bodies are free to define any syntax or > >semantics for the 3GPP2 OPTION_VENDOR_OPTS. So, if 3GPP2=20 > >coule require that a client sends a 3GPP2 OPTION_VENDOR_OPTS=20 > >request, which the server parses and responds with 3GPP2=20 > >OPTION_VENDOR_OPTS containing information for the client. > > > > > >- Ralph > > > > > >At 03:08 PM 10/28/2004 -0400, Kuntal Chowdhury wrote: > >>Hello Bernie, > >> > >>Thanks for the response. I guess what is not clear to me is > >how a DHCP > >>client requests vendor specific information from the DHCP server: > >> > >>" > >>- A Client includes OPTION_VENDOR_CLASS to identify itself. > >>- A Client MAY include OPTION_VENDOR_OPTS if it has vendor specific > >>data (other than classing information) to communicate. > >>- A Server includes OPTION_VENDOR_OPTS for matching=20 > >enterprise IDs (and > >>class data, if appropriate). This is only REQUIRED if the ORO > >includes > >>the OPTION_VENDOR_OPTS code (the ORO doesn't say which > >vendors; that is > >>handled by OPTION_VENDOR_CLASS). " > >> > >>Second bullet seems to say that the DHCP client includes > >>OPTION_VENDOR_OPTS to convey some vendor specific=20 > information to the=20 > >>DHCP server beside the vendor class info (which is in=20 > >>OPTION_VENDOR_CLASS). It does not state that OPTION_VENDOR_OPTS is=20 > >>included in a DHCP message (such as information > >>request) to REQUEST for vendor specific info from the server.=20 > >It is true > >>that opcode for OPTION_VENDOR_OPTS can be included in ORO, > >but that won't > >>necessarily indicate to the server which vendor specific > >codes it needs to > >>return to the client. Also, the format of the > >OPTION_VENDOR_OPTS when it > >>appears in the REQUEST message is unclear. > >> > >>A clear description of how to use OPTION_VENDOR_OPTS to > >request vendor > >>specific information (such as broadcast server address) will be > >>required by SDOs such as 3GPP2. > >> > >>Regards, > >>Kuntal > >> > >> > >> >-----Original Message----- > >> >From: Bernie Volz [mailto:volz@cisco.com] > >> >Sent: Wednesday, October 27, 2004 8:34 PM > >> >To: Chowdhury, Kuntal [RICH1:2H18:EXCH]; 'Ralph Droms' > >> >Cc: dhcwg@ietf.org > >> >Subject: RE: [dhcwg] BCMCS server option drafts > >> > > >> > > >> >Hi: > >> > > >> >I believe the original model was for OPTION_VENDOR_CLASS to be > >> >similar to DHCPv4 Vendor class identifier option (option=20 > >60) and for > >> >OPTION_VENDOR_OPTS to be similar to DHCPv4 Vendor Specific > >> >Information (option 43). > >> > > >> >You might refer to draft-ietf-dhc-vendor-03.txt, while for > >DHCPv4, it > >> >does have some additional information about how the options > >might be > >> >used. That work is modeled on the DHCPv6 options. In > >particular, see > >> >section 4: > >> > > >> >4. Vendor-Identifying Vendor-Specific Information Option > >> > > >> > DHCP clients and servers may use this option to=20 > exchange vendor- > >> > specific information. Either party may send this > >option, as needed. > >> > While a typical case might be for a client to send the > >> > Vendor-Identifying Vendor Class option, to elicit a useful > >> > Vendor-Identifying Vendor-Specific Information Option, > >there is no > >> > requirement for such a flow. > >> > > >> >It would be good to get general agreement on this as=20 > you're perhaps > >> >the first user. And, it would be best to set a "standard"=20 > >for others > >> >to follow. > >> > > >> >I kind of liked the DHCPv4 model, as it is much easier and > >clearly to > >> >understand (and implement for clients and servers): > >> >- A Client includes OPTION_VENDOR_CLASS to identify itself. > >> >- A Client MAY include OPTION_VENDOR_OPTS if it has=20 > vendor specific > >> >data (other than classing information) to communicate. > >> >- A Server includes OPTION_VENDOR_OPTS for matching=20 > enterprise IDs=20 > >> >(and class data, if appropriate). This is only REQUIRED=20 > if the ORO=20 > >> >includes the OPTION_VENDOR_OPTS code (the ORO doesn't say which=20 > >> >vendors; that is handled by OPTION_VENDOR_CLASS). > >> >- I'm not sure why a server would ever need to include=20 > >> >OPTION_VENDOR_CLASS, though perhaps it could tell the client what=20 > >> >implementation the server is so that perhaps the client knows it=20 > >> >could use some extended capabilities? Or, the server could=20 > >send back > >> >whatever the client sent to it? > >> > > >> >But, as draft-ietf-dhc-vendor-03.tx states, this is not the only > >> >possible model. > >> > > >> >Note that in your case, I would assume that the=20 > OPTION_VENDOR_CLASS > >> >would have your enterprise ID and some class information to=20 > >indicate > >> >what capabilities the client supports (and therefore the server > >> >should provide configuration for in the OPTION_VENDOR_OPTS). > >> > > >> >So, this is a good issue for the DHC WG to resolve and > >clarify for a > >> >future RFC 3315bis. > >> > > >> >- Bernie > >> > > >> >> -----Original Message----- > >> >> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On > >> >> Behalf Of Kuntal Chowdhury > >> >> Sent: Wednesday, October 27, 2004 4:33 PM > >> >> To: Ralph Droms; volz@cisco.com > >> >> Cc: dhcwg@ietf.org > >> >> Subject: RE: [dhcwg] BCMCS server option drafts > >> >> > >> >> > >> >> I have a few questions on the possible use of DHCPv6 > >> >> OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS to request vendor=20 > >> >> specific info: > >> >> > >> >> 1. Since the enterprise number is included in=20 > OPTION_VENDOR_OPTS, > >> >> will it suffice to use only this option in the=20 > >information request > >> >> message from the DHCP client? Is the use of OPTION_VENDOR_CLASS > >> >> mandatory while vendor specific options are requested? > >> >> > >> >> 2. Does the mere inclusion of OPTION_VENDOR_OPTS in the > >information > >> >> request message indicate to the DHCP server that the DHCP > >client is > >> >> requesting for some specific vendor specific options? > >> >> > >> >> 3. O-R-O has the format where each of requested option codes are > >> >> listed in it. However, in OPTION_VENDOR_OPTS the encapsulated=20 > >> >> vendor-specific options field MUST be encoded as a sequence of=20 > >> >> code/length/value fields. What value does the DHCP client=20 > >use while > >> >> requesting for a vendor specific option? > >> >> > >> >> These things are not clearly defined in RFC3315. > >> >> > >> >> Regards, > >> >> Kuntal > >> >> > >> >> >-----Original Message----- > >> >> >From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On > >> >> >Behalf Of Ralph Droms > >> >> >Sent: Wednesday, October 27, 2004 2:29 PM > >> >> >To: dhcwg@ietf.org > >> >> >Subject: RE: [dhcwg] BCMCS server option drafts > >> >> > > >> >> > > >> >> > > >> >> >What about the deployment issue? The 3GGP2=20 > specification will be > >> >> >ratified in November, with deployment following soon. Some=20 > >> >> >service providers already have DHCP servers in place=20 > that must be > >> >updated for > >> >> >any new options. The options defined in the current drafts can > >> >> >likely be supported without code changes to existing servers,=20 > >> >> >allowing for faster deployment. Use of a VIVSO=20 > sub-option would=20 > >> >> >require code changes to existing servers. How long would > >> >it take to > >> >> >deploy DHCP server that can support VIVSO? > >> >> > > >> >> >BTW, we need more discussion of this issue *soon* due to > >the time > >> >> >constraints of the upcoming 3GPP2 standards process and > >> >> >deployment. > >> >> > > >> >> >- Ralph > >> >> > > >> >> >At 04:12 PM 10/21/2004 -0400, Bernie Volz wrote: > >> >> >>Personally, I'd like to see the DHCPv4 VIVSO get deployed > >> >> and pushing > >> >> >>these options to using it would be a step at making this > >> >> >happen (as one > >> >> >>would expect 3GPP2 vendors to have some significant > >input to the > >> >> >>decisions of DHCP server vendors). > >> >> >> > >> >> >>It also means that 3GPP2 is free to define other VIVSO > >> >> options in the > >> >> >>future within their own forum and need not go to the IETF > >> >> >(and DHC WG). > >> >> >>I suspect that this would provide much faster deployment > >> >for them in > >> >> >>the future. > >> >> >> > >> >> >>Also, the DHCPv6 OPTION_VENDOR_CLASS and OPTION_VENDOR_OPTS > >> >> >are already > >> >> >>there for DHCPv6. > >> >> >> > >> >> >>BTW, 3GPP2 already has an enterprise-id number: > >> >> >> > >> >> >>5535 > >> >> >> 3rd Generation Partnership Project 2 (3GPP2) > >> >> >> Allen Long > >> >> >> along@cisco.com > >> >> >> > >> >> >>So, they'd be good to go! > >> >> >> > >> >> >>- Bernie > >> >> >> > >> >> >> > -----Original Message----- > >> >> >> > From: dhcwg-bounces@ietf.org=20 > [mailto:dhcwg-bounces@ietf.org] > >> >> >> > On Behalf Of Ralph Droms > >> >> >> > Sent: Thursday, October 21, 2004 2:35 PM > >> >> >> > To: dhcwg@ietf.org > >> >> >> > Subject: [dhcwg] BCMCS server option drafts > >> >> >> > > >> >> >> > > >> >> >> > We need to have a short WG conversation about two options > >> >> >that were > >> >> >> > discussed at the WG meeting in San Diego. The > >outcome of the > >> >> >> > conversation will be to determine consensus about taking > >> >> on these > >> >> >> > two > >> >> >> > drafts: > >> >> >> > > >> >> >> > draft-chowdhury-dhc-bcmcv4-option-01.txt > >> >> >> > draft-chowdhury-dhc-bcmcv6-option-01.txt > >> >> >> > > >> >> >> > as dhc WG work items or recommending that 3GPP2 define > >> >> >> > vendor-identifying vendor-specific option (VIVSO;=20 > option code > >> >> >> > 125) sub-options to carry the information described in > >> >> the drafts. > >> >> >> > > >> >> >> > If the WG consensus is to take on the drafts as WG > >work items > >> >> >> > drafts, are they acceptable as currently published? > >> >> >> > > >> >> >> > Because of the time constraints imposed by the 3GPP2 > >> >> schedule, I'm > >> >> >> > going to cut off discussion on this topic next Thursday, > >> >> >10/28, and > >> >> >> > determine WG consensus at that time. > >> >> >> > > >> >> >> > Here are some considerations for discussion: > >> >> >> > > >> >> >> > 3GPP2 has defined some vendor-specific sub-options, for > >> >> >example, to > >> >> >> > identify a MIP home agent for the DHCP client. > >> >> >> > > >> >> >> > A 3GPP2 client needs to specify to the DHCP server which > >> >> >parameters > >> >> >> > it needs - specifically, whether it needs to receive > >the BCMCS > >> >> >> > servers. If the current drafts are adopted, the client > >> >> can simply > >> >> >> > use the parameter request list option (option code > >55) for the > >> >> >> > request. If a VIVSO sub-option is used, 3GPP2 would > >> >> also define a > >> >> >> > parameter request list sub-option. > >> >> >> > > >> >> >> > There is a deployment issue, as some service providers > >> >> >already have > >> >> >> > DHCP servers in place that must be updated for any new > >> >> >options. Is > >> >> >> > it the case that the options defined in the current > >> >drafts can be > >> >> >> > supported without code changes to existing servers? Use > >> >> >of a VIVSO > >> >> >> > sub-option would require code changes to existing servers. > >> >> > How long > >> >> >> > would it take to deploy DHCP server that can support VIVSO. > >> >> >> > > >> >> >> > BCMCS may be adopted across multiple technologies, so the > >> >> >options in > >> >> >> > the current drafts would not be specific to 3GPP2. > >> >However, the > >> >> >> > BCMCS specification has not adopted by other standards, > >> >> yet, so we > >> >> >> > may need to define additional options for related > >> >> services in the > >> >> >> > future if those services are not interoperable with the > >> >> >3GPP2 BCMCS > >> >> >> > service. > >> >> >> > > >> >> >> > CableLabs has one option with sub-options (RFC 3495) > >> >rather than > >> >> >> > multiple options because: > >> >> >> > * wanted to avoid exhaustion of DHCP option code space; > >> >> >perhaps less > >> >> >> > of an issue with option code reclassification > >> >> >> > * would have used VIVSO if available > >> >> >> > * use of VIVSO with sub-options would give 3GPP2 freedom > >> >> >to define new > >> >> >> > sub-options on demand > >> >> >> > Do these considerations have an impact on our decision > >> >> >about how to > >> >> >> > proceed with the 3GPP2 options? > >> >> >> > > >> >> >> > - Ralph > >> >> >> > > >> >> >> > > >> >> >> > _______________________________________________ > >> >> >> > dhcwg mailing list > >> >> >> > dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg > >> >> >> > > >> >> > > >> >> > > >> >> >_______________________________________________ > >> >> >dhcwg mailing list > >> >> >dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg > >> >> > > >> >> > > >> >> > >> >> _______________________________________________ > >> >> dhcwg mailing list > >> >> dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg > >> >> > >> > > >> > > >> > > >> > >>_______________________________________________ > >>dhcwg mailing list > >>dhcwg@ietf.org > >>https://www1.ietf.org/mailman/listinfo/dhcwg > > > > > > >=20 > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg >=20 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Oct 29 16:47: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 QAA09829 for ; Fri, 29 Oct 2004 16:47:23 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNdt1-0001b9-4k for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 17:02:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNcm6-0005br-VO; Fri, 29 Oct 2004 15:51:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNcgB-00075G-3v for dhcwg@megatron.ietf.org; Fri, 29 Oct 2004 15:44:55 -0400 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 PAA29565 for ; Fri, 29 Oct 2004 15:44:52 -0400 (EDT) Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNcuV-00070j-LN for dhcwg@ietf.org; Fri, 29 Oct 2004 15:59:44 -0400 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9TJiKhP028004 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 29 Oct 2004 12:44:21 -0700 (PDT) Received: from WLAU.qualcomm.com (wlau.qualcomm.com [129.46.74.167]) by neophyte.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9TJiI9A014934; Fri, 29 Oct 2004 12:44:18 -0700 (PDT) Message-Id: <6.0.0.22.2.20041029121509.044f45e0@qcmail1.qualcomm.com> X-Sender: wlau@qcmail1.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 29 Oct 2004 12:44:17 -0700 To: "Kuntal Chowdhury" , Wing Cheong Lau From: Wing Cheong Lau Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and RADIUS Attributes sub-option In-Reply-To: <591B780D9676844E8A704B5B013FFE92038DE296@zrc2hxm1.corp.nor tel.com> References: <591B780D9676844E8A704B5B013FFE92038DE296@zrc2hxm1.corp.nortel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610 Dear Kuntal, Thank you for your comments. My response is interlaced below: At 12:04 PM 10/29/2004, Kuntal Chowdhury wrote: >I don't see the need for the following in the draft: > >1. Reference to 3GPP2: because 3GPP2 does not use the scheme that you are >proposing here. I disagree. At a minimum, the proposed option will benefit 3GPP2 in the case where the RADIUS and DHCP service are all under the same domain. In particular, the current way (835D) 3GPP2 uses RADIUS/DHCPv6. for doing MIP6 bootstrapping requires the PDSN to act as a DHCPv6 server (to answer stateless request for HA/HoA/HL info). On the other hand, there are also additional needs in 3GPP2 where the PDSN has to act as a relay-agent instead. Such dual role of PDSN is unnecessary and not desirable because it forces the Mobile to issue multiple separate requests for different set of parameters, to be answered by different DHCP servers. With the proposed option, the PDSN only needs to be serve as a relay-agent, and the mobile do not need to issue separate requests the different parameters it requests. >2. Vendor specific attribute parsing requirement on the DHCP server: It does >not scale. I do not see your point. It option is used as a "hint", if the DHCP server does not understand a specific vendor attribute, it can just ignore it while making it's assignment. What's the scalability issue here ? >3. The requirement of other parameter (non IP address) assignment by the >DHCP server: because the examples you give viz. HA, HoA, Home Link prefix >etc. are not something that the local domain (ASP) control as per MIP6. >These are controlled by the Home/Serving MSP. Sorry, I do not get your point. If the proposed option is deemed to be useful for a cross-domain RADIUS envirnoment, then, the HA/HoA/Home-link prefix, will be coming from the Home MSP, via RADIUS 3GPP VSA's, while the DHCPv6 relay-agent (PDSN) and the corresponding DHCPv6 server is under the control of the local domain ASP. This does not contradict your statement above. I do agree that it is valid to debate whether one should allow the Home MSP to push HA/HoA/HL info to its own DHCPv6 server. But regardless of the answer to this question, as I explain above, the proposed option do have value for the single-domain case where the RADIUS service and the DHCP servers/relay-agents are belonging to the same domain. Regards, Wing >-Kuntal > > >-----Original Message----- >From: Wing Cheong Lau [mailto:lau@qualcomm.com] >Sent: Friday, October 29, 2004 1:38 PM >To: Chowdhury, Kuntal [RICH1:2H18:EXCH] >Cc: dhcwg@ietf.org >Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option and >RADIUS Attributes sub-option > > >At 09:43 AM 10/29/2004, you wrote: > >A few questions on this draft: > >1. The primary motivation seems to be 3GPP2's network, but fact of the >matter is, 3GPP2 NAS (PDSN) does not push information received from a >different domain into the DHCP server in the local domain. > >Yes. That is the status quo. But the intent of the internet draft is to keep > >the possibility of such protocol support for roaming mobile scenario in the >future. >Of course, as clearly stated in the current draft regarding it's >applicability and >security implication need to be considered. In particular: > >"The scope of applicability of this specification is such that the NAS > (which acts as a DHCP relay agent), any other participating DHCP > relay agent, the DHCP server and DHCP client should be within the > same administrative domain while the RADIUS service involved may span > multiple administrative domains. See the Section 5 for details of > security considerations when this specification is deployed with > RADIUS service operating across multiple administrative domains. > Global interoperability of this specification, across arbitrary > administrative domains, is not supported. " > >and > >"The RADIUS protocol [6] was designed for intra-domain use, where the > NAS, proxy, and home server exist within a single administrative > domain, and proxies may be considered a trusted component. However, > under roaming situation, the NAS, proxies, and home server will > typically be managed by different administrative entities. As a > result, inter-domain RADIUS operations are inherently required for > roaming applications, and proxies cannot necessarily be trusted. > Refer to Section 7 of RFC 2609 for a detailed security threat > analysis, limitations and precautions of operating RADIUS in a inter- > domain environment. In general, robust and secure operations of > RADIUS across multiple administrative domains require pre-established > agreement, mutual trust, and secure communications channel amongst > all the participating domains." > >Inter-domain RADIUS operations have its well-known >set of risks and limitations and any future applications of the proposed >options >in an cross-domain environment would be subjected to such considerations. > > > > >2. The draft allows vendor specific RADIUS attributes to be pushed to the >DHCP server potentially from different domains. How does the DHCP sever >parse these vendor specific RADIUS attributes? Is it the assumption that the >DHCP server needs to know possibly all vendor specific RADIUS attributes? >This does not scale. > >In general, as specified in the draft, the DHCP server "MAY" use the >information carried in the proposed option as a HINT to make the subsequent >assignment. If the DHCP server does not >understand a particular vendor-specific option/VSA, it is free to ignore it >when making its >assignment. On the other hand, given a specific deployment environment, it >is not unreasonable to >assume the DHCP server would understand a particular set of vendor-specific, >e.g. 3GPP2, RADIUS VSA's. After all, as stated in the applicability >statement above, we are not talking about cross-domain RADIUS services over >any arbitrary domain, but only over those which have some sort of >pre-established roaming agreements. > > > >3. It says that the DHCP server uses this RADIUS info to do IP address >allocation and other parameter allocation. It would be nice to know what >other parameters the authors have in mind. > >Regards, >Kuntal > >Parameters under considerations included Home Agent address, (for dynamic HA >assignment), >Home Address (HoA) and/or Home-link prefix, etc. > >In fact, my understanding is that, for a single >domain environment, RADIUS 3GPP2 VSA's have already been defined for these >set of >parameters to enable MIP6 bootstrapping via RADIUS/DHCPv6 within a single >domain. > >If the risks/limitations of cross-domain RADIUS service stated above are >deemed to be acceptable, >there is a possibility that such bootstrapping scheme can be extended across >providers with >pre-established roaming agreements. > >Regards, > >Wing _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From dhcwg-bounces@ietf.org Fri Oct 29 17:47: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 RAA17265 for ; Fri, 29 Oct 2004 17:47:04 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNeom-0003UR-SP for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 18:01:57 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNeDk-0000pH-LH; Fri, 29 Oct 2004 17:23:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNdlk-0005Ga-Hq for dhcwg@megatron.ietf.org; Fri, 29 Oct 2004 16:54:44 -0400 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 QAA10952 for ; Fri, 29 Oct 2004 16:54:42 -0400 (EDT) Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNe06-0001o1-8w for dhcwg@ietf.org; Fri, 29 Oct 2004 17:09:34 -0400 Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i9TKsBE07036 for ; Fri, 29 Oct 2004 16:54:11 -0400 (EDT) Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 29 Oct 2004 16:54:11 -0400 Message-ID: <591B780D9676844E8A704B5B013FFE92038DE51E@zrc2hxm1.corp.nortel.com> From: "Kuntal Chowdhury" To: Wing Cheong Lau Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option an d RADIUS Attributes sub-option Date: Fri, 29 Oct 2004 16:54:01 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: a3f7094ccc62748c06b21fcf44c073ee Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bb031f3a6fb29f760794ac9bf1997ae The intent in your draft i.e. configure MN with HA/HoA/HL information can be achieved with: http://www.ietf.org/internet-drafts/draft-chowdhury-dhc-mip6-agentop-00.txt Unlike your draft this draft: 1. Does not require the DHCP server to parse vendor-specific RADIUS attributes. 2. Has no interdomain (ASP-MSP) tight coupling assumption. 3. Provides integrity and authenticity of the information that is exchanged. 4. It is AAA protocol agnostic, i.e. works for both RADIUS and DIAMETER. 5. Does not assume a 3GPP2 centric architecture. It is generic. Regards, Kuntal >-----Original Message----- >From: Wing Cheong Lau [mailto:lau@qualcomm.com] >Sent: Friday, October 29, 2004 2:44 PM >To: Chowdhury, Kuntal [RICH1:2H18:EXCH]; Wing Cheong Lau >Cc: dhcwg@ietf.org >Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information >Option and RADIUS Attributes sub-option > > >Dear Kuntal, > >Thank you for your comments. My response is interlaced below: > >At 12:04 PM 10/29/2004, Kuntal Chowdhury wrote: >>I don't see the need for the following in the draft: >> >>1. Reference to 3GPP2: because 3GPP2 does not use the scheme that you >>are proposing here. > >I disagree. At a minimum, the proposed option will benefit >3GPP2 in the >case where the RADIUS and DHCP service are all under the same >domain. In particular, the current way (835D) 3GPP2 uses >RADIUS/DHCPv6. for doing MIP6 bootstrapping requires the PDSN >to act as a DHCPv6 server >(to answer stateless >request for HA/HoA/HL info). On the other hand, there are also >additional >needs in 3GPP2 where the PDSN has to act as a relay-agent >instead. Such >dual role of PDSN is unnecessary and not desirable >because it forces the Mobile to issue multiple separate requests for >different set of parameters, to be answered by different DHCP servers. > >With the proposed option, the PDSN only needs to be serve as a >relay-agent, >and the mobile do not >need to issue separate requests the different parameters it requests. > >>2. Vendor specific attribute parsing requirement on the DHCP >server: It >>does not scale. >I do not see your point. It option is used as a "hint", if the >DHCP server >does not understand a specific >vendor attribute, it can just ignore it while making it's assignment. >What's the scalability issue here ? > >>3. The requirement of other parameter (non IP address) assignment by >>the DHCP server: because the examples you give viz. HA, HoA, >Home Link >>prefix etc. are not something that the local domain (ASP) control as >>per MIP6. These are controlled by the Home/Serving MSP. > >Sorry, I do not get your point. If the proposed option is deemed to be >useful for a cross-domain >RADIUS envirnoment, then, the HA/HoA/Home-link prefix, will be >coming from >the Home MSP, >via RADIUS 3GPP VSA's, while the DHCPv6 relay-agent (PDSN) and the >corresponding DHCPv6 server is under the control of the local >domain ASP. >This does not contradict your statement above. > >I do agree that it is valid to debate whether one should allow >the Home MSP >to push HA/HoA/HL info to its own DHCPv6 server. But regardless of the >answer to this question, as I explain above, the proposed >option do have >value for the single-domain case where the RADIUS service and >the DHCP servers/relay-agents are belonging to the same domain. > >Regards, > >Wing > > > > > > > >>-Kuntal >> >> >>-----Original Message----- >>From: Wing Cheong Lau [mailto:lau@qualcomm.com] >>Sent: Friday, October 29, 2004 1:38 PM >>To: Chowdhury, Kuntal [RICH1:2H18:EXCH] >>Cc: dhcwg@ietf.org >>Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option >>and RADIUS Attributes sub-option >> >> >>At 09:43 AM 10/29/2004, you wrote: >> >>A few questions on this draft: >> >>1. The primary motivation seems to be 3GPP2's network, but >fact of the >>matter is, 3GPP2 NAS (PDSN) does not push information received from a >>different domain into the DHCP server in the local domain. >> >>Yes. That is the status quo. But the intent of the internet >draft is to >>keep >> >>the possibility of such protocol support for roaming mobile >scenario in >>the future. Of course, as clearly stated in the current draft >regarding >>it's applicability and >>security implication need to be considered. In particular: >> >>"The scope of applicability of this specification is such that the NAS >> (which acts as a DHCP relay agent), any other participating DHCP >> relay agent, the DHCP server and DHCP client should be within the >> same administrative domain while the RADIUS service >involved may span >> multiple administrative domains. See the Section 5 for details of >> security considerations when this specification is deployed with >> RADIUS service operating across multiple administrative domains. >> Global interoperability of this specification, across arbitrary >> administrative domains, is not supported. " >> >>and >> >>"The RADIUS protocol [6] was designed for intra-domain use, where the >> NAS, proxy, and home server exist within a single administrative >> domain, and proxies may be considered a trusted >component. However, >> under roaming situation, the NAS, proxies, and home server will >> typically be managed by different administrative entities. As a >> result, inter-domain RADIUS operations are inherently required for >> roaming applications, and proxies cannot necessarily be trusted. >> Refer to Section 7 of RFC 2609 for a detailed security threat >> analysis, limitations and precautions of operating RADIUS >in a inter- >> domain environment. In general, robust and secure operations of >> RADIUS across multiple administrative domains require >pre-established >> agreement, mutual trust, and secure communications channel amongst >> all the participating domains." >> >>Inter-domain RADIUS operations have its well-known >>set of risks and limitations and any future applications of the >>proposed options in an cross-domain environment would be subjected to >>such considerations. >> >> >> >> >>2. The draft allows vendor specific RADIUS attributes to be pushed to >>the DHCP server potentially from different domains. How does the DHCP >>sever parse these vendor specific RADIUS attributes? Is it the >>assumption that the DHCP server needs to know possibly all vendor >>specific RADIUS attributes? This does not scale. >> >>In general, as specified in the draft, the DHCP server "MAY" use the >>information carried in the proposed option as a HINT to make the >>subsequent assignment. If the DHCP server does not understand a >>particular vendor-specific option/VSA, it is free to ignore it when >>making its assignment. On the other hand, given a specific deployment >>environment, it is not unreasonable to >>assume the DHCP server would understand a particular set of >vendor-specific, >>e.g. 3GPP2, RADIUS VSA's. After all, as stated in the applicability >>statement above, we are not talking about cross-domain RADIUS >services over >>any arbitrary domain, but only over those which have some sort of >>pre-established roaming agreements. >> >> >> >>3. It says that the DHCP server uses this RADIUS info to do >IP address >>allocation and other parameter allocation. It would be nice to know >>what other parameters the authors have in mind. >> >>Regards, >>Kuntal >> >>Parameters under considerations included Home Agent address, (for >>dynamic HA assignment), Home Address (HoA) and/or Home-link prefix, >>etc. >> >>In fact, my understanding is that, for a single >>domain environment, RADIUS 3GPP2 VSA's have already been defined for >>these set of parameters to enable MIP6 bootstrapping via >RADIUS/DHCPv6 >>within a single domain. >> >>If the risks/limitations of cross-domain RADIUS service stated above >>are deemed to be acceptable, there is a possibility that such >>bootstrapping scheme can be extended across providers with >>pre-established roaming agreements. >> >>Regards, >> >>Wing > > > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From Michaelefg@neptune.net Fri Oct 29 18:01:39 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 SAA18499; Fri, 29 Oct 2004 18:01:39 -0400 (EDT) Received: from user-0cdvdgi.cable.mindspring.com ([24.223.182.18]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNf2t-0003oU-BI; Fri, 29 Oct 2004 18:16:32 -0400 X-Message-Info: VLIXyOY15iEHmIu199d0+TYLCv0zGQZY Received: from mail491.btf.optusnet.com.au ([132.150.19.97]) by lj69-b7.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Fri, 29 Oct 2004 19:54:17 -0200 Received: from JDAN65 (p1.26.124.72.bxvdc1.lzh.optusnet.com.au [96.174.11.153]) by mail275.ddl.optusnet.com.au (30.77.1i8/8.48.3) with SMTP id o4J12Zc43234; Sat, 30 Oct 2004 01:01:17 +0300 Message-ID: <29n033j8ni7b$fc8x59x9$id3820p4@OWGC81> From: "Graham Crabtree" To: "Bmwg-admin" References: Subject: special offer for Fireworks MX 2004 Date: Fri, 29 Oct 2004 21:00:17 -0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--2-962292264-0798633154=:50671" X-Spam-Score: 13.9 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 ----2-962292264-0798633154=:50671 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable TOP Brands Software:

Special Offer #3:
Macromedia Dreamwaver MX 20= 04 + Flash MX 2004 =3D only $290

Special Offer #1:
Windows XP Professional+Microso= ft Office XP Professional =3D only $80
Special Offer #2:
Adobe - Photoshop 7, Premiere 7, = Illustrator 29 =3D only $120
Also:
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
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
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
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

Enter Here









bertrand breezemaze billy amongstbelch dietary escapadebambi alphabet trailvalue mollusk finnyglenda cantabrigian brighthiram hued knuckleconfound readout chemicdrunkard hedonism octillioneuphoric ----2-962292264-0798633154=:50671-- From dhcwg-bounces@ietf.org Fri Oct 29 18:30:00 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 SAA21595 for ; Fri, 29 Oct 2004 18:30:00 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNfUL-0004NR-VE for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 18:44:54 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNf9Q-0005KF-Bf; Fri, 29 Oct 2004 18:23:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNetO-0001SO-NV for dhcwg@megatron.ietf.org; Fri, 29 Oct 2004 18:06:42 -0400 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 SAA19448 for ; Fri, 29 Oct 2004 18:06:40 -0400 (EDT) Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNf7k-0003yP-Ug for dhcwg@ietf.org; Fri, 29 Oct 2004 18:21:33 -0400 Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150]) by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9TM68hP009487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 29 Oct 2004 15:06:09 -0700 (PDT) Received: from WLAU.qualcomm.com (wlau.qualcomm.com [129.46.74.167]) by sabrina.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9TM65HJ019518; Fri, 29 Oct 2004 15:06:06 -0700 (PDT) Message-Id: <6.0.0.22.2.20041029135901.0454ec30@qcmail1.qualcomm.com> X-Sender: wlau@qcmail1.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 29 Oct 2004 15:06:05 -0700 To: "Kuntal Chowdhury" , Wing Cheong Lau From: Wing Cheong Lau Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option an d RADIUS Attributes sub-option In-Reply-To: <591B780D9676844E8A704B5B013FFE92038DE51E@zrc2hxm1.corp.nor tel.com> References: <591B780D9676844E8A704B5B013FFE92038DE51E@zrc2hxm1.corp.nortel.com> Mime-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: df9edf1223802dd4cf213867a3af6121 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0757723456==" Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a4a24b484706be629f915bfb1a3e4771 --===============0757723456== Content-Type: multipart/alternative; boundary="=====================_491981712==.ALT" --=====================_491981712==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Kuntal, At 01:54 PM 10/29/2004, Kuntal Chowdhury wrote: >The intent in your draft i.e. configure MN with HA/HoA/HL information can be >achieved with: > >http://www.ietf.org/internet-drafts/draft-chowdhury-dhc-mip6-agentop-00.txt Thanks for bringing to our attention the existence of this new draft. Somehow, I have not seen its announcement before, at least not in the dhc or mip6 mailing list. >Unlike your draft this draft: > >1. Does not require the DHCP server to parse vendor-specific RADIUS >attributes. But it requires the DHCP relay-agent to parse and understand the newly defined, yet-to-be standardized RADIUS Attributes carrying HA/HoA/Home-link-prefix as described in draft-chowdhury-mip6-bootstrap-radius-00.txt and similar yet-to-be defined attributes if DIAMETER is used. >2. Has no interdomain (ASP-MSP) tight coupling assumption. >3. Provides integrity and authenticity of the information that is exchanged. >4. It is AAA protocol agnostic, i.e. works for both RADIUS and DIAMETER. >5. Does not assume a 3GPP2 centric architecture. It is generic. >Regards, >Kuntal I just did a quick pass thru it but did not find any description addressing the issue where the NAS/DHCP relay-agent and the AAA belongs to a different domain and RADIUS is used as the AAA protocol. (This is precisely the same issue you raised for the DHCPv6 Relay Information Option/RADIUS Attributes sub-option draft.). So, would you point to the specific text in the draft which substantiates your claims 2) and 4) simultaneously ? Currently, the draft just conveniently states: "The AAA procedures using RADIUS is defined in [MIP6-RADIUS]", but [MIP6-RADIUS] Chowdhury et. al., K., "RADIUS Attributes for Mobile IPv6 bootstrapping", draft-chowdhury-mip6-bootstrap-radius-01 (work in progress), July 2004. cannot be found in public (I meant -01 version cannot be found, only -00 is available). On the other hand, I cannot see how the cross-domain scenario described in -00 version of draft-chowdhury-mip6-bootstrap-radius the draftis different than the one in draft-droms-dhc-v6-relayopt-00.txt. Am I missing something here ? I would also like to point out that the DHCPv6 Relay Info Option/ RADIUS Attribute sub-option actually addresses 2 level of needs: 1. The ability of DHCPv6 Relay agent to tag along additional "info" as it forwards requests from the DHCP client to the DHCP server, regardless of the specific nature of the "info". This is a "general" capability for the DHCPv6 Relay agent which is absent from the RFC 3315. It seems like both your and our draft needs such capability. The main difference is that, in draft-chowdhury-dhc-mip6-agentop-00.txt, newly defined MIP6-bootstrapping options are relayed while in draft-droms-dhc-v6-relayopt-00.txt, the info got relayed are RADIUS attributes. 2. As for the relay-agent RADIUS option, it is a feature of its own right, the example given in our draft is just one of its use which can help address an immediate issue in 3GPP2 835D. 3. As stated in draft-droms-dhc-v6-relayopt-00.txt, " This document uses 3GPP2 access authentication as an example to motivate the use of the Relay Agent Information option and the RADIUS Attributes sub-option by a NAS. The Relay Agent Information option is not limited to use in conjunction with RADIUS sub-option when other sub-options are defined in the future. The RADIUS Attributes sub- option for the Relay Agent Information option described in this document is not limited to use in conjunction with 3GPP2 and can be used to carry RADIUS attributes obtained by the relay agent for any reason. That is, the sub-option is not limited to use with 3GPP2, but is constrained by RADIUS semantics." Regards, Wing --=====================_491981712==.ALT Content-Type: text/html; charset="us-ascii" Kuntal,

At 01:54 PM 10/29/2004, Kuntal Chowdhury wrote:
The intent in your draft i.e. configure MN with HA/HoA/HL information can be
achieved with:

http://www.ietf.org/internet-drafts/draft-chowdhury-dhc-mip6-agentop-00.txt

Thanks for bringing to our attention the existence of this new draft. Somehow, I have not seen
its announcement before, at least not in the dhc or mip6 mailing list.

Unlike your draft this draft:

1. Does not require the DHCP server to parse vendor-specific RADIUS
attributes.

But it requires the DHCP relay-agent to parse and understand the newly defined, yet-to-be standardized RADIUS Attributes carrying HA/HoA/Home-link-prefix as described in
draft-chowdhury-mip6-bootstrap-radius-00.txt and similar yet-to-be
defined attributes if DIAMETER is used.

2. Has no interdomain (ASP-MSP) tight coupling assumption.
3. Provides integrity and authenticity of the information that is exchanged.
4. It is AAA protocol agnostic, i.e. works for both RADIUS and DIAMETER.
5. Does not assume a 3GPP2 centric architecture. It is generic.


Regards,
Kuntal


I just did a quick pass thru it but did not find any description addressing the issue where
the NAS/DHCP relay-agent and the AAA belongs to a different domain and RADIUS is used as
the AAA protocol. (This is precisely the same issue you raised for the DHCPv6 Relay Information Option/RADIUS Attributes sub-option draft.). So, would you point to the specific text in the draft which substantiates your claims 2) and 4) simultaneously ?

Currently, the draft just conveniently states:
"The AAA procedures using RADIUS is defined in [MIP6-RADIUS]",
but

   [MIP6-RADIUS]
             
Chowdhury et. al., K., "RADIUS Attributes for Mobile IPv6
             
bootstrapping", draft-chowdhury-mip6-bootstrap-radius-01
             
(work in progress), July 2004.

cannot be found in public (I meant -01 version cannot be found, only -00 is available).
On the other hand, I cannot see how the cross-domain scenario described in  -00 version of 
draft-chowdhury-mip6-bootstrap-radius
the draftis different than the one in draft-droms-dhc-v6-relayopt-00.txt.

Am I missing something here ?


I would also like to point out that the DHCPv6 Relay Info Option/ RADIUS Attribute sub-option actually addresses 2 level of  needs:

1. The ability of DHCPv6 Relay agent to tag along additional "info" as it forwards requests from the DHCP client to the DHCP server, regardless of the specific nature of the "info". This is a "general"
capability for the DHCPv6 Relay agent which is absent from the RFC 3315. It seems like both your
and our draft needs such capability. The main difference is that, in draft-chowdhury-dhc-mip6-agentop-00.txt, newly defined MIP6-bootstrapping options are relayed while in draft-droms-dhc-v6-relayopt-00.txt, the info got relayed are RADIUS attributes.


2. As for the relay-agent RADIUS option, it is a feature of its own right, the example given in our draft is just one of its use which can help address an immediate issue in 3GPP2 835D.


3. As stated in draft-droms-dhc-v6-relayopt-00.txt,
" This document uses 3GPP2 access authentication as an example to
   motivate the use of the Relay Agent Information option and the RADIUS
   Attributes sub-option by a NAS. The Relay Agent Information option is
   not limited to use in conjunction with RADIUS sub-option when other
   sub-options are defined in the future. The RADIUS Attributes sub-
   option for the Relay Agent Information option described in this
   document is not limited to use in conjunction with 3GPP2 and can be
   used to carry RADIUS attributes obtained by the relay agent for any
   reason.  That is, the sub-option is not limited to use with 3GPP2,
   but is constrained by RADIUS semantics."


Regards,

Wing --=====================_491981712==.ALT-- --===============0757723456== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg --===============0757723456==-- From dhcwg-bounces@ietf.org Fri Oct 29 18:54:19 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 SAA23155 for ; Fri, 29 Oct 2004 18:54:18 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNfrs-0004pm-R7 for dhcwg-web-archive@ietf.org; Fri, 29 Oct 2004 19:09:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNfZD-0004hd-KS; Fri, 29 Oct 2004 18:49:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNfOZ-0004GT-59 for dhcwg@megatron.ietf.org; Fri, 29 Oct 2004 18:38:55 -0400 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 SAA22291 for ; Fri, 29 Oct 2004 18:38:52 -0400 (EDT) Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNfcv-0004Y7-Lb for dhcwg@ietf.org; Fri, 29 Oct 2004 18:53:46 -0400 Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i9TMcMX25964 for ; Fri, 29 Oct 2004 18:38:22 -0400 (EDT) Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 29 Oct 2004 18:38:22 -0400 Message-ID: <591B780D9676844E8A704B5B013FFE92038DE6C9@zrc2hxm1.corp.nortel.com> From: "Kuntal Chowdhury" To: Wing Cheong Lau Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option a n d RADIUS Attributes sub-option Date: Fri, 29 Oct 2004 18:38:10 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290 Cc: dhcwg@ietf.org X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c draft-chowdhury-mip6-bootstrap-radius-01.txt is not publicly available yet because I submitted -01 version after the 25th Nov cutoff date. It will be available after Nov 7th when the new submission gate opens. If you need, I can send you a copy. BTW, the DHCP relay does not do AAA AVP parsing. The NAS which is collocated with the DHCP relay does the parsing. Don't you think AAA AVP parsing is in the job description of a NAS? -Kuntal -----Original Message----- From: Wing Cheong Lau [mailto:lau@qualcomm.com] Sent: Friday, October 29, 2004 5:06 PM To: Chowdhury, Kuntal [RICH1:2H18:EXCH]; Wing Cheong Lau Cc: dhcwg@ietf.org Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option an d RADIUS Attributes sub-option Kuntal, At 01:54 PM 10/29/2004, Kuntal Chowdhury wrote: The intent in your draft i.e. configure MN with HA/HoA/HL information can be achieved with: http://www.ietf.org/internet-drafts/draft-chowdhury-dhc-mip6-agentop-00.txt Thanks for bringing to our attention the existence of this new draft. Somehow, I have not seen its announcement before, at least not in the dhc or mip6 mailing list. Unlike your draft this draft: 1. Does not require the DHCP server to parse vendor-specific RADIUS attributes. But it requires the DHCP relay-agent to parse and understand the newly defined, yet-to-be standardized RADIUS Attributes carrying HA/HoA/Home-link-prefix as described in draft-chowdhury-mip6-bootstrap-radius-00.txt and similar yet-to-be defined attributes if DIAMETER is used. 2. Has no interdomain (ASP-MSP) tight coupling assumption. 3. Provides integrity and authenticity of the information that is exchanged. 4. It is AAA protocol agnostic, i.e. works for both RADIUS and DIAMETER. 5. Does not assume a 3GPP2 centric architecture. It is generic. Regards, Kuntal I just did a quick pass thru it but did not find any description addressing the issue where the NAS/DHCP relay-agent and the AAA belongs to a different domain and RADIUS is used as the AAA protocol. (This is precisely the same issue you raised for the DHCPv6 Relay Information Option/RADIUS Attributes sub-option draft.). So, would you point to the specific text in the draft which substantiates your claims 2) and 4) simultaneously ? Currently, the draft just conveniently states: "The AAA procedures using RADIUS is defined in [MIP6-RADIUS]", but [MIP6-RADIUS] Chowdhury et. al., K., "RADIUS Attributes for Mobile IPv6 bootstrapping", draft-chowdhury-mip6-bootstrap-radius-01 (work in progress), July 2004. cannot be found in public (I meant -01 version cannot be found, only -00 is available). On the other hand, I cannot see how the cross-domain scenario described in -00 version of draft-chowdhury-mip6-bootstrap-radius the draftis different than the one in draft-droms-dhc-v6-relayopt-00.txt. Am I missing something here ? I would also like to point out that the DHCPv6 Relay Info Option/ RADIUS Attribute sub-option actually addresses 2 level of needs: 1. The ability of DHCPv6 Relay agent to tag along additional "info" as it forwards requests from the DHCP client to the DHCP server, regardless of the specific nature of the "info". This is a "general" capability for the DHCPv6 Relay agent which is absent from the RFC 3315. It seems like both your and our draft needs such capability. The main difference is that, in draft-chowdhury-dhc-mip6-agentop-00.txt, newly defined MIP6-bootstrapping options are relayed while in draft-droms-dhc-v6-relayopt-00.txt, the info got relayed are RADIUS attributes. 2. As for the relay-agent RADIUS option, it is a feature of its own right, the example given in our draft is just one of its use which can help address an immediate issue in 3GPP2 835D. 3. As stated in draft-droms-dhc-v6-relayopt-00.txt, " This document uses 3GPP2 access authentication as an example to motivate the use of the Relay Agent Information option and the RADIUS Attributes sub-option by a NAS. The Relay Agent Information option is not limited to use in conjunction with RADIUS sub-option when other sub-options are defined in the future. The RADIUS Attributes sub- option for the Relay Agent Information option described in this document is not limited to use in conjunction with 3GPP2 and can be used to carry RADIUS attributes obtained by the relay agent for any reason. That is, the sub-option is not limited to use with 3GPP2, but is constrained by RADIUS semantics." Regards, Wing _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From taagdqwo@chartertn.net Fri Oct 29 20:25:34 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 UAA28823; Fri, 29 Oct 2004 20:25:34 -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 1CNhIA-0006RU-PO; Fri, 29 Oct 2004 20:40:28 -0400 Received: from myl-c-24-159-180-149.chartertn.net ([24.159.180.149]) by mx2.foretec.com with smtp (Exim 4.24) id 1CNh3p-0001tV-0k; Fri, 29 Oct 2004 20:25:38 -0400 Received: from myl-c-24-159-180-149.chartertn.net by mail.chartertn.net with HTTP; Fri, 29 Oct 2004 18:12:46 -0600 Received: from 45.19.153.16 by myl-c-24-159-180-149.chartertn.net with HTTP; Fri, 29 Oct 2004 18:11:38 -0600 Date: Fri, 29 Oct 2004 18:12:22 -0600 Message-ID: <000301c4be0c$cd6d3db0$90b8f2a7@EYLSSENJS> From: "Les" Content-Type: text/plain; charset="ISO-8859-8" Subject: to keep the money Mime-Version: 1.0 To: disman@ietf.org Cc: dccp-request@ietf.org, entmib-request@ietf.org, dhcwg-web-archive@ietf.org Content-Transfer-Encoding: 7bit X-Spam-Score: 6.0 (++++++) X-Spam-Flag: YES X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 7bit This notification was sent using automated system. Please process to stop the auto-generated email. Fri, 29 Oct 2004 18:12:46 -0600 A pprov a l Account Statement Security Control Number: 1013-3630-0509-5343 Offer Expiration Date: 11/17/04 Interest Ra t e: 3.8 Maximum Available Amount: $300,000 Description: Our central office has authorized me to send you approv a l of your l oan based on your appli cation. Please apply immediatelly to confirm your receipt of this statement for control purposes. http://www.nokalko.com/ Thank you. Les, Manager From igaxzblhtkfsk@flash.net Sat Oct 30 06:34:56 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 GAA14000; Sat, 30 Oct 2004 06:34:55 -0400 (EDT) Received: from chello082119098233.chello.sk ([82.119.98.233]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNqnz-0007i0-27; Sat, 30 Oct 2004 06:49:56 -0400 X-Message-Info: 166wwHBmvtVIH3NEHkofI515JKY86CNdmEFyruzMUNhId19MK Received: from cox.net (24.130.124.130) by f5-e614.cox.net with Microsoft SMTPSVC(1.3.4269.7649); Sat, 30 Oct 2004 10:24:00 -0100 Received: from cox.net (cox.net 200.216.24.3) by cox.net (8.12.10/8.12.9) with ESMTP id rp489I227 for ; Sat, 30 Oct 2004 17:28:00 +0600 (EST) (envelope-from igaxzblhtkfsk@flash.net) Received: from XXM57791236218 (modemcable183.73815-8.e.cox.net 184.24.168.124) (authenticated bits=7) by cox.net (8.12.10/8.12.9) with ESMTP id mc71C3hq986 for ; Sat, 30 Oct 2004 13:22:00 +0200 (EST) (envelope-from igaxzblhtkfsk@flash.net) Message-ID: <673gc463oa7$tq6g31hrv038$85cj6mge3@F3868303> From: "Unlimited Movie" To: Subject: Unlimited Music and Movie Downloads -u Date: Sat, 30 Oct 2004 10:25:00 -0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--00293816032853517188" X-Spam-Score: 2.6 (++) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f ----00293816032853517188 Content-Type: text/plain; Content-Transfer-Encoding: quoted-printable Hello Experience & Enjoy the Digital revolution. We at- File Sharing Center -announces future of online entertainment. Download anything you could possibly want in 3 simple, fast, and easy steps- START DOWNLOADING NOW! This service is 100 percent safe, Secure and Legal http://www.rosewoodsearch.com/ref91.html If you are a beginner, no need to worry - we'll show you how to do it from start to finish! We've made it so easy, you'll be downloading anything you could possibly = want This Service Comes With: Un limited =B7 Music & MP3s =B7 Movies =B7 Games =B7 Software =B7 TV Shows =B7 Song Lyrics =B7 Audio Books More Bonuses: =B7 DVD Copying Software =B7 MP3 Burning Software =B7 Anti-Virus Software =B7 Game Copying Software =B7 Pop-Up/Spyware/Adware Killer Software http://www.rosewoodsearch.com/ref91.html =B7 Even More Benefits : =B7 Latest FileSharing Software =B7 In-Depth Visual Tutorials =B7 Internet History Cleaner =B7 Privacy Protection Software =B7 Access to 90,000,000 Songs =B7 Unlimited Technical Support =B7 Stay Legal - Don't Get Sued Lifetime Membership is only $34.95! Check out to Join Now and Start Downloading in Minutes! http://www.rosewoodsearch.com/ref91.html Regards Elias Pike Sales Manager File Sharing Center http://www.rosewoodsearch.com/ref91.html To Discountinue-- http://jmabeik.cd-digishop.info/soft/chair.php -------------------- parochial genre operon polaron kodachrome isolate scatterbrain gravitate l= eatherwork bowditch prophylactic anne collard scm crabapple dichotomous te= te gaillardia cheeky gesticulate warden shortage tuscany cartoon duplicate= milord consume perk adduce enervate attainder humanoid trimer fibrin appr= ehension minibike eggplant blackfeet salvation soiree bedrock defunct stop= barnet staff antic appall bronzy redneck tun lever cleveland agnomen nica= ragua houston maggoty dioxide dowager uri susan boric cinderella contrariw= ise charlie bauhaus grade noteworthy stop equanimity gustafson uri conserv= ation sweat neuroanatomic hubris widowhood r's willis depute gumption abst= inent patrolled toiletry berkeley peaceable darling batten scheme astral a= rtichoke diatribe spector essex crew tumbrel bounce fusillade big forgetfu= l charismatic announce dross cobweb whitehorse yipping eleanor secretion m= onopoly nozzle lehigh holt freehand westfield across ha chump tetrahedral = boxy siren brucellosis alias troposphere imperceivable strength pawn margo= mingle ancestry architectural town liar croft prostrate possemen loretta = catholicism adapt anthropomorphism u indefinite quonset manhattan quadrila= teral disciple wichita officio dolores acrobacy aerial circumpolar bolshoi= theses inevitable phantasy stressful eave nuptial bolshevik farthest chor= data deceptive rowley anode hungry slight barnard pituitary treason clergy= man farewell shasta temptation cinerama collie cutler thrush depredate mat= rimonial cachalot burro astound board dietz segment crude chorus yvette be= at cork camel gelatin sterling enlargeable house wayne pogo bitten chromat= ic sawyer incorporate motet galena expansion tilde law fourier verdict cur= vilinear journal skeleton ajax clement trim affectation hydrothermal diffe= rentiate mitchell multitude splashy binghamton algenib command triennial v= ivify blanch paula societal schmidt donate shirt breve charta saloon garbl= e journey bustle denver bootleg freer creamy encomia velours dyeing arraig= n burroughs minuet innkeeper dialysis prague wilmington illicit jettison b= ang smoothbore apprise savannah lesbian debate jewelry goldenrod airdrop f= aze albrecht laidlaw corrugate contretemps earthquake balled merle litterb= ug flagstone herd layout natural populist peer exceptional hire besetting = compulsory perceptual castle sociable =20 ----00293816032853517188-- From Garciaowhuc@dotcom.fr Sat Oct 30 11:46:08 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 LAA00486; Sat, 30 Oct 2004 11:46:08 -0400 (EDT) Received: from cpe-065-185-196-254.nc.rr.com ([65.185.196.254]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNvf6-0004Jl-Nf; Sat, 30 Oct 2004 12:01:11 -0400 Received: from fight.xglobe.com.sg ([173.218.222.93]) by 65.185.196.254 with ESMTP id <92027672269086.NVUS44001.combatant@siutao.com> for ; Sat, 30 Oct 2004 19:45:42 +0300 Date: Sat, 30 Oct 2004 11:45:42 -0500 From: "Jo Morton" Reply-To: "Jo Morton" Message-Id: <050953e819h3065a64t6273d6s3868@regard> Organization: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) To: dccp@ietf.org, dccp-admin@ietf.org, dccp-request@ietf.org, dhcwg@ietf.org, dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, dinaras@ietf.org, directory-web-archive@ietf.org, enum@ietf.org, enum-admin@ietf.org, enum-archive@ietf.org, enum-request@ietf.org, iab@ietf.org, iesg@ietf.org Subject: is his boyfriend still in pain X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0-502456003-6952728296=:66161" X-Spam-Score: 9.7 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: 79899194edc4f33a41f49410777972f8 --0-502456003-6952728296=:66161 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable




Remove




horsetail mariannecongratulate hun bijouterienaomi mispronunciation bayeddairy algebraic attainflamboyant contentious goldfishfeatherbedding meritorious bimetallicrotary partisan infestprovost stubborn dwellhumanoid bimini clytemnestraconscious --0-502456003-6952728296=:66161-- From Loveqry@ultimanet.com Sat Oct 30 13:14: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 NAA05773; Sat, 30 Oct 2004 13:14:09 -0400 (EDT) Received: from adsl-68-126-236-37.dsl.pltn13.pacbell.net ([68.126.236.37]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CNx2N-000628-E2; Sat, 30 Oct 2004 13:29:14 -0400 Received: from walkover.ccom.net ([18.40.236.240) by dreamy.ccom.net (InterMail vK.4.80.72.67 793-411-741-59140779 license mfqvx5yz38192tq3865l55lr2139h4910) with ESMTP id <34230260146006.XRKL873.foregoing@mckesson.ccom.net> for ; Sat, 30 Oct 2004 23:08:59 +0500 Received: from nullpmws4esytf (collocation-477-735.ccom.net [34.62.151.0]) by song.ccom.net (Mirapoint Messaging Server EDP 1.3.2-NG) with SMTP id QAF73004; Fri, 12 Dec 2003 00:05:06 +0200 (IST) Message-ID: <001d01c3c032$d5749130$fa8be650@nullpmws4esytf> From: "Max Farleyl" To: Subject: half price Microsoft Windows XP Home Date: Sat, 30 Oct 2004 14:04:59 -0400 MIME-Version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Content-type: multipart/alternative; boundary="----=_NextPart_3-526766677-2986947834=:16821" X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 11.7 (+++++++++++) X-Spam-Flag: YES X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 This is a multi-part message in MIME format. ------=_NextPart_3-526766677-2986947834=:16821 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -------------------------------------------------------------------------= ------- ------=_NextPart_3-526766677-2986947834=:16821 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable GREAT MICROSOFT DEAL:
We might have just what you need.

Windows XP Professional 20= 02 ............. $50
Adobe Photoshop 7.0 .........= ............ $60
Microsoft Office XP Professio= nal 2002 .... $60
Corel Draw Graphics Suite 11= ............. $60

and lots more...







= passband bamakolarynges specious chentutelage wellesley combinatedollar diocesan acerbitycarmela single bizarreconspiracy mansion crabmeatanionic dogmatism aimdadaism jackpot bantucheater coeducation irmaclytemnestra ------=_NextPart_3-526766677-2986947834=:16821-- From Englandjzan@tngi.com Sat Oct 30 16:35: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 QAA16975; Sat, 30 Oct 2004 16:35:26 -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 1CO0BD-0001BM-6c; Sat, 30 Oct 2004 16:50:31 -0400 Received: from clt74-102-159.carolina.rr.com ([24.74.102.159]) by mx2.foretec.com with smtp (Exim 4.24) id 1CNz7l-0003Cn-Hl; Sat, 30 Oct 2004 15:42:54 -0400 Message-ID: <02201131062808.770lnt28552wc@hotmail.com> Received: from 96.100.144.149 by law4-st27.law9.hotmail.com with DAV; Mon, 20 Oct 2003 06:14:26 +0500 Reply-To: "Lea Crouch" From: "Lea Crouch" To: Subject: assist your daughter with her pain Date: Mon, 20 Oct 2003 06:07:26 +0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--1-885042816-7272579572=:89693" X-Spam-Score: 8.9 (++++++++) X-Spam-Flag: YES X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c ----1-885042816-7272579572=:89693 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable 0NL1NE PHARMACY
St0p pay1ng the 1nflated pharmacy pr1ces
These gener1c meds are 1dent1cal t0 branded types!
ALL AT 1NCRED1BLE PR1CES!
Check 0ut 0ur c0mplete 1n= vent0ry

NEW - V1COD1N
NEW - PHENTERM1NE
0RDER N0W
free sh1pp1ng 1n november

Also:
Gener1c V*1agra
Gener1c C*1al1s
Branded X*en1cal
Gener1c M*er1d1a
Gener1c P*r0pec1a
Gener1c G*luc0phage
Gener1c V*10xx
Gener1c C*elebrex
Gener1c P*ax1l
Gener1c Z*0l0ft
Gener1c L*1p1t0r





R*E*M**0V*E ME


dote lambdawardroom hoagland galenitekingbird individuate diocesanpragmatic bruno gratedemo broach footstoolafterword sleep paroleerode layout nctopmost sprague yosemitebevy benedictine inflationaryabash ----1-885042816-7272579572=:89693-- From cyfetwgcerlzy@catchamail.com Sun Oct 31 01:27:22 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 BAA14781; Sun, 31 Oct 2004 01:27:21 -0400 (EDT) Received: from [61.78.122.98] (helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CO8Tq-00015P-1H; Sun, 31 Oct 2004 01:42:30 -0400 X-Message-Info: ZA/ow+2+u/CFE+215/0756706676 Received: from smtp-gullah.bravery.cyfetwgcerlzy@catchamail.com ([61.78.122.98]) by g05-pkc3.cyfetwgcerlzy@catchamail.com with Microsoft SMTPSVC(5.0.5289.4603); Sun, 31 Oct 2004 01:19:55 -0500 Received: from smtp-doomsday.coddle.cyfetwgcerlzy@catchamail.com ([61.78.122.98]) by ew8-zd08.cyfetwgcerlzy@catchamail.com with Microsoft SMTPSVC(5.0.1414.0504); Sat, 30 Oct 2004 23:18:55 -0700 X-Message-Info: YIJEV+%ND_LC_CHAR[1-3]1+n+FP+885/80091829388840 Received: (qmail 59794 invoked by uid 4); Sun, 31 Oct 2004 10:17:55 +0500 Date: Sun, 31 Oct 2004 10:18:55 +0500 Message-Id: <6729337246220.92073@cyfetwgcerlzy@catchamail.com> From: Daphne Larkin To: Entmib MIME-Version: 1.0 (produced by storebaseboard 3.0) Content-Type: multipart/alternative; boundary="--7423643579122700762" X-Spam-Score: 13.5 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 ----7423643579122700762 Content-Type: text/html; charset="iso-1021-0" Content-Description: enormous cepheus sockeye Content-Transfer-Encoding: quoted-printable

Looking for a way to save money?

Paying a h= igh percentage on your mortgage?

Get a 3.5%and start saving those hard earned dollars!!

Fill in an easy 1 minute application and start saving = hundreds of dollars monthly!

Why pay more, if you can pay less = and spend the money on something else?!

Fill in Here<= /b>

----7423643579122700762-- From dhcwg-bounces@ietf.org Sun Oct 31 01:55:03 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 BAA16011 for ; Sun, 31 Oct 2004 01:55:03 -0400 (EDT) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CO8up-0001W6-ST for dhcwg-web-archive@ietf.org; Sun, 31 Oct 2004 01:10:12 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CO8bs-0008Oh-Kj; Sun, 31 Oct 2004 01:50:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CO8Ws-0007bu-UN for dhcwg@megatron.ietf.org; Sun, 31 Oct 2004 01:45:26 -0400 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 BAA15572 for ; Sun, 31 Oct 2004 01:45:26 -0400 (EDT) Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CO8lW-0001M2-0O for dhcwg@ietf.org; Sun, 31 Oct 2004 01:00:34 -0500 Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149]) by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9V5ireD016031 for ; Sat, 30 Oct 2004 22:44:53 -0700 (PDT) Received: from WLAU.qualcomm.com (qconnect-10-50-68-119.qualcomm.com [10.50.68.119]) by neophyte.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id i9V5io9A018758 for ; Sat, 30 Oct 2004 22:44:51 -0700 (PDT) Message-Id: <6.0.0.22.2.20041030224427.03fb2630@qcmail1.qualcomm.com> X-Sender: wlau@qcmail1.qualcomm.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Sat, 30 Oct 2004 22:44:50 -0700 To: dhcwg@ietf.org From: Wing Cheong Lau Subject: RE: [dhcwg] New draft on DHCPv6 Relay Information Option a n d RADIUS Attributes sub-option Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 3971661e40967acfc35f708dd5f33760 X-BeenThere: dhcwg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: dhcwg.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: dhcwg-bounces@ietf.org Errors-To: dhcwg-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba >Date: Sat, 30 Oct 2004 11:23:40 -0700 >To: "Kuntal Chowdhury" >From: Wing Cheong Lau >Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option a >n d RADIUS Attributes sub-option > >At 03:38 PM 10/29/2004, you wrote: >>draft-chowdhury-mip6-bootstrap-radius-01.txt is not publicly available yet >>because I submitted -01 version after the 25th Nov cutoff date. It will be >>available after Nov 7th when the new submission gate opens. If you need, I >>can send you a copy. > >>-Kuntal > >Sure, a URL for that draft will be welcome. Thanks in advance. >(BTW, the reference date for -01 should be >Oct 04, rather than July 04, as currently shown in >draft-chowdhury-dhc-mip6-agentop-00.txt then). > >In any case, would you share with us in advance how the proposed scheme >addresses the trust/security >issue for the case where the NAS/DHCP relay-agent and the AAA belong to >different domains >and RADIUS is used as the AAA protocol ? >This is to substantiate the support of claims 2) and 4) simultaneously ? > > >Regards, > >Wing > > > >>-----Original Message----- >>From: Wing Cheong Lau [mailto:lau@qualcomm.com] >>Sent: Friday, October 29, 2004 5:06 PM >>To: Chowdhury, Kuntal [RICH1:2H18:EXCH]; Wing Cheong Lau >>Cc: dhcwg@ietf.org >>Subject: RE: RE: [dhcwg] New draft on DHCPv6 Relay Information Option an d >>RADIUS Attributes sub-option >> >> >>Kuntal, >> >>At 01:54 PM 10/29/2004, Kuntal Chowdhury wrote: >> >>The intent in your draft i.e. configure MN with HA/HoA/HL information can be >>achieved with: >> >>http://www.ietf.org/internet-drafts/draft-chowdhury-dhc-mip6-agentop-00.txt >> >> >>Thanks for bringing to our attention the existence of this new draft. >>Somehow, I have not seen >>its announcement before, at least not in the dhc or mip6 mailing list. >> >> >>Unlike your draft this draft: >> >>1. Does not require the DHCP server to parse vendor-specific RADIUS >>attributes. >> >>But it requires the DHCP relay-agent to parse and understand the newly >>defined, yet-to-be standardized RADIUS Attributes carrying >>HA/HoA/Home-link-prefix as described in >> >>draft-chowdhury-mip6-bootstrap-radius-00.txt and similar yet-to-be >>defined attributes if DIAMETER is used. >> >> >>2. Has no interdomain (ASP-MSP) tight coupling assumption. >>3. Provides integrity and authenticity of the information that is exchanged. >>4. It is AAA protocol agnostic, i.e. works for both RADIUS and DIAMETER. >>5. Does not assume a 3GPP2 centric architecture. It is generic. >> >> >> >> >>Regards, >>Kuntal >> >> >> >>I just did a quick pass thru it but did not find any description addressing >>the issue where >>the NAS/DHCP relay-agent and the AAA belongs to a different domain and >>RADIUS is used as >>the AAA protocol. (This is precisely the same issue you raised for the >>DHCPv6 Relay Information Option/RADIUS Attributes sub-option draft.). So, >>would you point to the specific text in the draft which substantiates your >>claims 2) and 4) simultaneously ? >> >> >>Currently, the draft just conveniently states: >>"The AAA procedures using RADIUS is defined in [MIP6-RADIUS]", >>but >> >> [MIP6-RADIUS] >> >>Chowdhury et. al., K., "RADIUS Attributes for Mobile IPv6 >> >>bootstrapping", draft-chowdhury-mip6-bootstrap-radius-01 >> >>(work in progress), July 2004. >> >> >>cannot be found in public (I meant -01 version cannot be found, only -00 is >>available). >>On the other hand, I cannot see how the cross-domain scenario described in >>-00 version of >>draft-chowdhury-mip6-bootstrap-radius >> >>the draftis different than the one in draft-droms-dhc-v6-relayopt-00.txt. >> >>Am I missing something here ? >> >> >>I would also like to point out that the DHCPv6 Relay Info Option/ RADIUS >>Attribute sub-option actually addresses 2 level of needs: >> >>1. The ability of DHCPv6 Relay agent to tag along additional "info" as it >>forwards requests from the DHCP client to the DHCP server, regardless of the >>specific nature of the "info". This is a "general" >>capability for the DHCPv6 Relay agent which is absent from the RFC 3315. It >>seems like both your >>and our draft needs such capability. The main difference is that, in >>draft-chowdhury-dhc-mip6-agentop-00.txt, newly defined MIP6-bootstrapping >>options are relayed while in draft-droms-dhc-v6-relayopt-00.txt, the info >>got relayed are RADIUS attributes. >> >> >>2. As for the relay-agent RADIUS option, it is a feature of its own right, >>the example given in our draft is just one of its use which can help address >>an immediate issue in 3GPP2 835D. >> >> >>3. As stated in draft-droms-dhc-v6-relayopt-00.txt, >>" This document uses 3GPP2 access authentication as an example to >> motivate the use of the Relay Agent Information option and the RADIUS >> Attributes sub-option by a NAS. The Relay Agent Information option is >> not limited to use in conjunction with RADIUS sub-option when other >> sub-options are defined in the future. The RADIUS Attributes sub- >> option for the Relay Agent Information option described in this >> document is not limited to use in conjunction with 3GPP2 and can be >> used to carry RADIUS attributes obtained by the relay agent for any >> reason. That is, the sub-option is not limited to use with 3GPP2, >> but is constrained by RADIUS semantics." >> >> >>Regards, >> >>Wing _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From prdtnhzgsotk@hotmail.com Sun Oct 31 03:28: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 DAA08058; Sun, 31 Oct 2004 03:28:07 -0500 (EST) Date: Sun, 31 Oct 2004 03:28:07 -0500 (EST) Received: from modemcable076.33-202-24.mc.videotron.ca ([24.202.33.76]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1COBIz-0003qN-Bx; Sun, 31 Oct 2004 03:43:17 -0500 Received: from 0.2.148.111 by 24.202.33.76; Sun, 31 Oct 2004 04:23:38 -0400 Message-ID: From: "Kennith Reeder" Reply-To: "Kennith Reeder" To: dhcwg@ietf.org Cc: dhcwg-admin@ietf.org, dhcwg-request@ietf.org, dhcwg-web-archive@ietf.org, diffserv-admin@ietf.org, diffserv-interest@ietf.org, diffserv-interest-admin@ietf.org, diffserv-interest-request@ietf.org, dinaras@ietf.org Subject: Sa-ve 70% of Regular Pr|ce Dhcwg X-Spam-Score: 5.9 (+++++) X-Spam-Flag: YES X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 User ID: 6 sandalwood Date: Sun, 31 Oct 2004 14:23:38 +0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--66157764428803799" ----66157764428803799 Content-Type: text/plain; Content-Transfer-Encoding: 7Bit Buy Med's 0n-line! Up to 8o% off Vi-c0din, Cia|is, V|agra, Xanax, Vioxx, Va|ium and many more! Fast delivery! with wholesale prices! -No Con^sultation -No Prior Prescription Needed -Hu'ge Savings! See why our customers re-order more than any competitor! http://bestpills.mythingsusa.com/?k=S17h49 This is 1 -time mailing. N0-re m0val are re'qui-red m3NVrT9qXz7KN0cnPAzEXvHDh0L3mhv ----66157764428803799-- From Holmanyhs@jpopmail.com Sun Oct 31 06:50:02 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 GAA17560; Sun, 31 Oct 2004 06:50:01 -0500 (EST) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COESD-0002lJ-Sp; Sun, 31 Oct 2004 07:05:13 -0500 Received: from [219.249.37.167] (helo=65.246.255.50) by mx2.foretec.com with smtp (Exim 4.24) id 1COEDT-00042U-GA; Sun, 31 Oct 2004 06:49:49 -0500 Received: from seguros.com.br ([207.246.96.175]) by mulberry.seguros.com.br (InterMail vK.4.04.00.00 139-090-212 license 6bd290ac7482d6ad2a9bdd7895a7dfc1) with ESMTP id <20031018214323.PNIV1929.mtacyclone@tripletec.com> for ; Sat, 18 Oct 2003 23:43:23 +0200 From: "info" To: "Galen Chandler" Subject: Re: New virus defenitions - september 26th Sender: "info" Date: Sun, 31 Oct 2004 15:42:35 +0400 MIME-Version: 1.0 Content-type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Message-ID: X-Spam-Score: 9.3 (+++++++++) X-Spam-Flag: YES X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit




Remove



your cladradar noun diagrammaticsolitary bernardo hypothesisglutinous lehman marshmallowtragic teensy irrationalwi cordial menopausenepal vestal leftwardaffair holden astrophysicsutrecht quahog harnesstenfold =20 From Lucerojcpu@wonet.com Sun Oct 31 07:14:47 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 HAA18959; Sun, 31 Oct 2004 07:14:47 -0500 (EST) Received: from c-24-125-105-255.va.client2.attbi.com ([24.125.105.255]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1COEqC-00035f-L0; Sun, 31 Oct 2004 07:29:59 -0500 X-Message-Info: ptxvm86Aueuwh22UNZkmDUfexYyaSVbjyM669 Received: from neuroanatomy-dns.xoom.com ([0.50.176.200]) by g1-gly4.xoom.com with Microsoft SMTPSVC(5.0.2195.6824); Sun, 31 Oct 2004 16:13:27 +0400 Date: Sun, 31 Oct 2004 16:09:27 +0400 (CST) Message-Id: <8596738030.KP4eNBqlr727@thieves644.stearic25xoom.com> To: avt@ietf.org Subject: your girlfriend needs to cope with the pain From: Elaine Flint MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--8-128580507-7460228619=:25040" X-Spam-Score: 12.1 (++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a ----8-128580507-7460228619=:25040 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Stop Hurting!
VIC0D1N - Pain Relief !
0rder



enough



mogadiscio picnickedmathieu incommutable denizencurry denotative shishabuse cub sourwoodallegation deregulate spruedavenport decontrolled steeralpha beatify isoldeclothesman wastage temptinsurance canopy embeddedangel ----8-128580507-7460228619=:25040-- From Lucerojcpu@wonet.com Sun Oct 31 07:15:06 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 HAA19015; Sun, 31 Oct 2004 07:15:06 -0500 (EST) Received: from woh-29-173-227.woh.rr.com ([24.29.173.227] helo=132.151.6.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1COEqg-00037A-2N; Sun, 31 Oct 2004 07:30:18 -0500 X-Message-Info: ptxvm86Aueuwh22UNZkmDUfexYyaSVbjyM669 Received: from neuroanatomy-dns.xoom.com ([0.50.176.200]) by g1-gly4.xoom.com with Microsoft SMTPSVC(5.0.2195.6824); Sun, 31 Oct 2004 16:13:27 +0400 Date: Sun, 31 Oct 2004 16:09:27 +0400 (CST) Message-Id: <8596738030.KP4eNBqlr727@thieves644.stearic25xoom.com> To: avt@ietf.org Subject: your girlfriend needs to cope with the pain From: Elaine Flint MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--8-128580507-7460228619=:25040" X-Spam-Score: 13.8 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a ----8-128580507-7460228619=:25040 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable Stop Hurting!
VIC0D1N - Pain Relief !
0rder



enough



mogadiscio picnickedmathieu incommutable denizencurry denotative shishabuse cub sourwoodallegation deregulate spruedavenport decontrolled steeralpha beatify isoldeclothesman wastage temptinsurance canopy embeddedangel ----8-128580507-7460228619=:25040-- From xozdlbkoy@swbell.net Sun Oct 31 07:17: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 HAA19817; Sun, 31 Oct 2004 07:17:33 -0500 (EST) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COEsr-00039O-4I; Sun, 31 Oct 2004 07:32:44 -0500 Received: from adsl-68-89-75-232.dsl.hrlntx.swbell.net ([68.89.75.232]) by mx2.foretec.com with smtp (Exim 4.24) id 1COEVQ-0004P4-4V; Sun, 31 Oct 2004 07:08:22 -0500 Received: from adsl-68-89-75-232.dsl.hrlntx.swbell.net by sbcmail1.prodigy.net with SMTP id 30616; Sun, 31 Oct 2004 04:55:33 -0600 Received: from 166.104.25.147 by adsl-68-89-75-232.dsl.hrlntx.swbell.net with HTTP; Sun, 31 Oct 2004 04:54:53 -0600 Subject: YOU bastard! ... You Message-ID: <3725753521892134.67150.ticweege@63.172.113.161> Content-Type: text/plain; charset="ISO-8859-8" Date: Sun, 31 Oct 2004 07:48:33 -0300 To: From: "Tracey M. Downs" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Score: 6.6 (++++++) X-Spam-Flag: YES X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit As you know election time is not the best thing for the economy. Economy is in a very unstable condition, as you can see gas prices are going up along with the m o rtgxage rat e s. Once the r a te goes up you will not have a chance to s av e money again for a very long time. It is your last chance. Get R e f inanced at 4.2 point! http://www.nokalko.com/ -- papal chen by cholera the demountable out from linen the Bblotch zen highwayman evanston From Rossbxnk@lycos.co.kr Sun Oct 31 07:44:24 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 HAA22969; Sun, 31 Oct 2004 07:44:23 -0500 (EST) Received: from yahoobb219019116151.bbtec.net ([219.19.116.151]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1COFJ0-0003hc-Cl; Sun, 31 Oct 2004 07:59:36 -0500 Received: from molest.jahoopa.com (molest.jahoopa.com [124.20.145.152]) by 219.19.116.151 with; Sun, 31 Oct 2004 18:43:07 +0600 Date: Sun, 31 Oct 2004 08:44:07 -0400 From: "Marion Jimenez" Reply-To: "Marion Jimenez" Message-ID: <843369r981d6551m46f4815d8i7956@corpsman> To: Tammy Subject: your daughter hurting X-Mailer: tissue Organization: Internet Mail Service (5.5.2650.21) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="6-762337245-3870132217=:47998" X-Spam-Score: 6.7 (++++++) X-Spam-Flag: YES X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 --6-762337245-3870132217=:47998 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable %MAKE_TXT[3-6] --6-762337245-3870132217=:47998 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable VIC0D1N
Pain Relief !
More info




enough



incondensable anthonyship deportation biminicowardice enthusiast boatloadearthmover visionary idahobinomial digit blondforage addressograph aventinebema adjoin controlledbestubble answer propagatemorrill osborn catniplighthouse --6-762337245-3870132217=:47998-- From Mohrczlt@sylvaninfo.net Sun Oct 31 17:56:39 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 RAA11535; Sun, 31 Oct 2004 17:56:39 -0500 (EST) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COOre-0007Lw-QP; Sun, 31 Oct 2004 18:11:59 -0500 Received: from user-0c9325n.cable.mindspring.com ([24.145.136.183]) by mx2.foretec.com with smtp (Exim 4.24) id 1COOcl-000147-Ma; Sun, 31 Oct 2004 17:56:36 -0500 X-Message-Info: 82TSEohg791j664TDlSS61n7ecRFRdalsLtwXYKjzu04glb Received: from nwinfo.net ([144.139.96.28]) by nwt2-kd3.nwinfo.net with Microsoft SMTPSVC(3.3.0493.2509); Mon, 01 Nov 2004 04:53:23 +0600 Received: from nwinfo.net (nwinfo.net [215.140.236.125]) by nwinfo.net (8.12.10/8.12.9) with ESMTP id fj00YFLJRTQ48002 for ; Sun, 31 Oct 2004 19:48:23 -0300 (EST) (envelope-from Mohrczlt@sylvaninfo.net) Received: from RPA37069745973 (modemcable857.03-1.hpt.nwinfo.net [184.232.60.158]) (authenticated bits=4) by nwinfo.net (8.12.10/8.12.9) with ESMTP id EEV1njd5ZIB706747 for ; Sun, 31 Oct 2004 21:51:23 -0100 (EST) (envelope-from Mohrczlt@sylvaninfo.net) Message-ID: <55365pbd12ehy247$gju1X264n9$21KDE036RD59@x548727> From: "Christa Conner" To: Subject: why does your daughter spy on you Date: Sun, 31 Oct 2004 16:50:23 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--7-326723688-1943066270=:16248" X-Spam-Score: 13.2 (+++++++++++++) X-Spam-Flag: YES X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a ----7-326723688-1943066270=:16248 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable CNET Digital:
Spyware is the leading cause for PC failure and hard drive corruption.
= Please scan your c= omputer


*r*e*l*e*a*s*e



supercilious ingestiondecrypt bellingham extensionmidpoint diagnosis itselfcure dodecahedra ascertainfeet aspire mienporosity serve drewhi raspberry husbandrytwigging crossarm extendsunset epistle winemakecorcoran ----7-326723688-1943066270=:16248-- From Novakdvu@allesklar.de Sun Oct 31 19:20:45 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 TAA17887; Sun, 31 Oct 2004 19:20:45 -0500 (EST) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COQB1-0000ST-SY; Sun, 31 Oct 2004 19:36:04 -0500 Received: from h000d56544471.ne.client2.attbi.com ([24.62.213.104]) by mx2.foretec.com with smtp (Exim 4.24) id 1COPw9-0003OZ-72; Sun, 31 Oct 2004 19:20:43 -0500 Received: from danbury.subotica.com ([84.67.13.34]) by hydrant.subotica.com (InterMail vK.4.04.00.00 201-232-137 license 6bd290ac7482d6ad2a9bdd7895a7dfc1) with ESMTP id <20030703164753.BOOS20985.homonym@generosity.subotica.com>; Thu, Sun, 31 Oct 2004 22:12:34 -0200 Received: from techsupp_014 (control.barak.net.il [206.49.94.149]) by newsletter.barak.net.il (Postfix) with ESMTP id A117DB7A42; Thu, 3 Jul 2003 20:04:46 +0300 (IDT) Message-ID: <41116-2200374317485441@techsupp_014> To: "" From: Wilmer Rasmussen Subject: Work and Live in the USA Date: Mon, 01 Nov 2004 03:12:34 +0300 MIME-Version: 1.0 Content-type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Spam-Score: 7.4 (+++++++) X-Spam-Flag: YES X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: quoted-printable










gerundial volitionexpense hebraic shirtcopybook ineligible pennfrantic flush harpoontear swingable berthamsterdam anguish forfeitshakeable decade athabascanasinine pollutant stickyarnold extolling baffinpeppy =20 From Hahnfam@ctsi.net Sun Oct 31 20:46: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 UAA23050; Sun, 31 Oct 2004 20:46:37 -0500 (EST) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CORW8-0001nn-A0; Sun, 31 Oct 2004 21:01:57 -0500 Received: from modemcable172.121-37-24.mc.videotron.ca ([24.37.121.172]) by mx2.foretec.com with smtp (Exim 4.24) id 1CORHC-00073x-W8; Sun, 31 Oct 2004 20:46:31 -0500 X-Message-Info: 5kVGpM11Zdtjta2tYjP1CE3kWpypbJ07 Received: from dns1denture.com ([144.246.16.4]) by ud8-p3.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Sun, 31 Oct 2004 18:46:28 -0700 Received: from everywherehold.com [127.0.0.1] by dns3fertile.com (SMTPD32-7.12 ) id YU800028T3; Mon, 01 Nov 2004 00:42:28 -0100 Subject: Microsoft Windows XP Critical Update - october 22th From: Wiley.Bravo To: dhcwg-web-archive@ietf.org Message-Id: <817425770542091.BK16388@propensitydoltish.com> Content-Type: multipart/alternative; boundary="--5-939466264-3633678602=:22260" Date: Sun, 31 Oct 2004 20:46:31 -0500 X-Spam-Score: 11.1 (+++++++++++) X-Spam-Flag: YES X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f ----5-939466264-3633678602=:22260 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable











aggregate dunlapbull columbine bilkappend alfred josephsondeceptive flush sternalburnt wiretapper heterocyclicdavit colby chelatearuba boone comprehensibleanhydrite seventeenth you'lltrihedral psychoanalyst daimlerhowsomever =20 ----5-939466264-3633678602=:22260--