From owner-pilc@grc.nasa.gov Fri Feb 1 06:18:16 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16532 for ; Fri, 1 Feb 2002 06:18:15 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 84494C6973 for ; Fri, 1 Feb 2002 06:17:24 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id GAA19961 for pilc-outgoing; Fri, 1 Feb 2002 06:11:53 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id GAA19957 for ; Fri, 1 Feb 2002 06:11:52 -0500 (EST) From: email@multiflex.co.kr Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id GAA19543 for ; Fri, 1 Feb 2002 06:11:51 -0500 (EST) Received: from com2 (unknown [218.48.35.52]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id F0907640CA for ; Fri, 1 Feb 2002 06:11:49 -0500 (EST) Received: from com2 ([169.254.236.137]) by com2 with Microsoft SMTPSVC(5.0.2195.2966); Fri, 1 Feb 2002 20:12:10 +0900 Subject: [¼ºÀα¤°í]¿µÈ­º¸´Â Áñ°Å¿òÀÌ °¡µæÇÑ ¿µÈ­°ü(¿ù5000¿ø).... Date: Fri, 01 Feb 2002 20:12:10 +0900 Message-Id: <37288.841790219907100.325773@localhost> MIME-Version: 1.0 Content-Type: text/html; charset=euc-kr Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 01 Feb 2002 11:12:10.0685 (UTC) FILETIME=[4B28E6D0:01C1AB11] Sender: owner-pilc@grc.nasa.gov Precedence: bulk To: undisclosed-recipients:; Content-Transfer-Encoding: 8bit Multiflex Mail
From owner-pilc@grc.nasa.gov Sat Feb 2 04:57:49 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01255 for ; Sat, 2 Feb 2002 04:57:49 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id A8BA164159 for ; Sat, 2 Feb 2002 04:57:13 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id EAA19407 for pilc-outgoing; Sat, 2 Feb 2002 04:51:19 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id EAA19393 for ; Sat, 2 Feb 2002 04:51:18 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id EAA29698 for ; Sat, 2 Feb 2002 04:51:16 -0500 (EST) Received: from localhost (s211-33-80-128.thrunet.ne.kr [211.33.80.128]) by seraph2.grc.nasa.gov (Postfix) with SMTP id 06B9AC6947 for ; Sat, 2 Feb 2002 04:49:55 -0500 (EST) Reply-To: kasdfasdf@lycos.co.kr From: ¸¶Äϵµ¿ì¹Ì To: pilc@grc.nasa.gov Subject: 15¸¸¿øÂ¥¸®Á¾ÇÕ¼îÇθô Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Sat, 2 Feb 2002 18:47:31 +0900 Message-Id: <20020202094955.06B9AC6947@seraph2.grc.nasa.gov> Sender: owner-pilc@grc.nasa.gov Precedence: bulk »ó¾÷¼º ±¤°í¸ÞÀÏÀ» º¸³»°Ô µÇ¾î¼­ Á¤¸»Á˼ÛÇÕ´Ï´Ù

15¸¸¿øÂ¥¸®Á¾ÇÕ¼îÇθô °ßº»º¸±â

¡Ý Á¦°ø¼­ºñ½º

¢ºÁÖ¹®, °áÀç, ¹è¼Û, Åùè½Ã½ºÅÛ
µî ¿Â¶óÀÎ »óÁ¡¿¡ ÇÊ¿ä·Î ÇÏ´Â ¸ðµç ½Ã½ºÅÛÀ» ¿ø½ºÅéÀ¸·Î Á¦°øÇϰí ÀÖ¾î,
Àç°í³ª ¹è¼ÛÀÇ ºÎ´ãÀÌ ÀüÇô ¾ø½À´Ï´Ù.

¢º°øµ¿±¸¸Å±â´É

¢º¹«·á¹®ÀÚ¸Þ¼¼Áö±â´É

¢º 20,000¿© »óǰ °ø±Þ°¡(µô·¯°¡)Á¦°ø..(¼ö½Ã ¾÷±×·¹À̵å)
       - Á¾ÇÕ¸ô ¹× Àü¹®¸ô ÇüÅ·Π¿î¿µÇÏ½Ç ¼ö ÀÖ½À´Ï´Ù..
¢º ÁÖ¹®, ¹è¼Û, ¹Ýǰ, »óǰ°ü¸® ¹°·ù ¿ø½ºÅé(One Stop)¼­ºñ½º ÀÌ¿ë
       - ÁÖ¹®¼­ ÀÛ¼º¸¸ ÇÏ½Ã¸é µË´Ï´Ù..(´ç»ç¿¡¼­ ¸ðµÎó¸®)
¢º ÇØÇÇÄݼ¾ÅÍ ÀÌ¿ë (ÁÖ¹®È®ÀÎ ¹× ¹è¼ÛÈ®ÀÎ Äݼ­ºñ½º)
       - °í°´(¼îÇθô)¿¡ ´ëÇÑ ½Å·Ú°¨ Çü¼º

ÀüÈ­»ó´ã¹Þ½À´Ï´Ù 053-641-4433ÀÎÅͳݻç¾÷ºÎ

9¸¸9õ¿øÂ¥¸® ȨÆäÀÌÁöÁ¦À۰ߺ»º¸±â

9¸¸9õ¿øÂ¥¸® ȨÆäÀÌÁö¸Þ´º¾óµÑ·¯º¸±â

¼ö½Å°ÅºÎÇÕ´Ï´Ù

´ÔÀÇ ¸ÞÀÏÁÖ¼Ò´Â ÀÎÅͳݿ©ÇàÀ» ÇÏ´Ù ¼öÁýÇÏ¿´À¾´Ï´Ù.

ÀúÈñ´Â ±ÍÇÏ¿¡ ´ëÇØ ¾î¶°ÇÑ Á¤º¸µµ °¡Áö°íÀÖÁö¾Ê½À´Ï´Ù

¼ö½Å°ÅºÎ¸¦ ÇØÁÖ½Ã¸é ´ÙÀ½ºÎÅÍ´Â µÎ¹ø´Ù½Ã ¸ÞÀÏÀ» º¸³»Áö ¾Ê°Ú½À´Ï´Ù

From owner-pilc@grc.nasa.gov Sat Feb 2 07:06:30 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02486 for ; Sat, 2 Feb 2002 07:06:29 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 7404DC69BF for ; Sat, 2 Feb 2002 07:05:55 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id HAA28745 for pilc-outgoing; Sat, 2 Feb 2002 07:00:13 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id HAA28739 for ; Sat, 2 Feb 2002 07:00:12 -0500 (EST) From: Viagra9520@eudoramail.com Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id HAA11247 for ; Sat, 2 Feb 2002 07:00:12 -0500 (EST) Received: from server1.autocisa.com (unknown [217.58.74.245]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 418FDC68E4 for ; Sat, 2 Feb 2002 06:59:55 -0500 (EST) Received: from mx1.eudoramail.com (SS [207.93.244.65]) by server1.autocisa.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 1C4S5GFF; Sat, 2 Feb 2002 13:05:59 +0100 Message-ID: <0000247112bf$00000583$00002d32@mx1.eudoramail.com> To: Subject: Make This Valentine's Day Unforgettable. TMSKOZW Date: Sat, 02 Feb 2002 06:00:14 -1800 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Reply-To: Viagra9520@eudoramail.com Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: quoted-printable = Orders Today will be Shipped Tomorrow


 

    • Orders Today will be Shipped Tomorrow
    • No Prescription Necessary
    • U.S. Doct= ors and Pharmacy available for co= nsultation
    • All orders shipped Fed Ex Overnight

 
 
 
 
To be removed from future mailing= s, please reply with "Remove" as subject.
 
From owner-pilc@grc.nasa.gov Tue Feb 5 11:37:57 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07175 for ; Tue, 5 Feb 2002 11:37:57 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id E1B49C69F0 for ; Tue, 5 Feb 2002 11:37:23 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id LAA27197 for pilc-outgoing; Tue, 5 Feb 2002 11:29:39 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id LAA27153; Tue, 5 Feb 2002 11:29:35 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id LAA09546; Tue, 5 Feb 2002 11:29:31 -0500 (EST) Received: from www.yahho.com (28.c210-85-16.ethome.net.tw [210.85.16.28]) by seraph3.grc.nasa.gov (Postfix) with SMTP id E6DDC6412C; Tue, 5 Feb 2002 11:27:42 -0500 (EST) Received: from venus by saturn.seed.net.tw with SMTP id Kb6NizXbmLibLtrj5Luth; Wed, 06 Feb 2002 00:36:32 +0800 Message-ID: From: 4P5PWjjkOL36nFm@hotmail.com To: lvWvyEf5gratb@ksts.seed.net.tw X-Mailer: QAfRs7pE2POO6Sx3 Content-Type: text/plain; X-Priority: 3 X-MSMail-Priority: Normal Date: Tue, 5 Feb 2002 11:27:42 -0500 (EST) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from Quoted-Printable to 8bit by lombok-fi.lerc.nasa.gov id LAB27182 Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 8bit ±ÀÂ˧A­Ì¤@­Ó¤£¿ùªººô¯¸---¼Æ¦ìµø³¥ ¦UºØ¼Æ¦ì¬Û¾÷ªºµû¤ñ»Pºô¤Íªº¤¬°Ê°Q½×,¥i¥H°µ¬°ÁʶR«eªº°Ñ¦Ò. ÁÙ´£¨Ñ¤F³\¦h¨R¬~¼Æ¦ì·Ó¤ùªºªù¥«¤Îºô¯¸,¥Ø«e4x6¤@±i¥u­n6¤¸! §ó¯S§Oªº¬O,ÁÙ¦³°O¾Ð¥dªº¥X¯²,§Ú¹L¦~¥X°ê´N¥´ºâ¦V¥L­Ì¯²°O¾Ð¥d,´N¤£¥Î§âNotebook¦ª¥X¥h! www.dcview.com.tw From owner-pilc@grc.nasa.gov Sat Feb 9 00:51:11 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04022 for ; Sat, 9 Feb 2002 00:51:11 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 4345064158 for ; Sat, 9 Feb 2002 00:50:36 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id AAA17871 for pilc-outgoing; Sat, 9 Feb 2002 00:39:48 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id AAA17808; Sat, 9 Feb 2002 00:39:41 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id AAA18225; Sat, 9 Feb 2002 00:39:39 -0500 (EST) Received: from www.yahho.com (28.c210-85-16.ethome.net.tw [210.85.16.28]) by seraph2.grc.nasa.gov (Postfix) with SMTP id 57782C691C; Sat, 9 Feb 2002 00:37:02 -0500 (EST) Received: from tpts7 by pavo.seed.net.tw with SMTP id eTZtEsjz6A8YY9DKJWgU7THX; Sat, 09 Feb 2002 13:45:59 +0800 Message-ID: From: uXSRT9B@kimo.com To: 9ReMFJssJ8@pchome.com.tw Subject: 0rwD2AjSUZxyHVuNdPxjOHyVx MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----=_NextPart_voYwEjHS1D0UbB2hqMCbY2A" X-Mailer: czzZxV5FY41ugoHRyXsyeuKc2 X-Priority: 3 X-MSMail-Priority: Normal Date: Sat, 9 Feb 2002 00:37:02 -0500 (EST) Sender: owner-pilc@grc.nasa.gov Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_voYwEjHS1D0UbB2hqMCbY2A Content-Type: multipart/alternative; boundary="----=_NextPart_voYwEjHS1D0UbB2hqMCbY2AAA" ------=_NextPart_voYwEjHS1D0UbB2hqMCbY2AAA Content-Type: text/html; charset="big5" Content-Transfer-Encoding: base64 PGh0bWw+DQoNCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50 PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9YmlnNSI+DQo8bWV0YSBuYW1lPSJHRU5FUkFUT1IiIGNvbnRl bnQ9Ik1pY3Jvc29mdCBGcm9udFBhZ2UgNC4wIj4NCjxtZXRhIG5hbWU9IlByb2dJZCIgY29udGVu dD0iRnJvbnRQYWdlLkVkaXRvci5Eb2N1bWVudCI+DQo8dGl0bGU+saGkSLhgxeW77rBPPC90aXRs ZT4NCjwvaGVhZD4NCg0KPGJvZHk+DQoNCjxwPq+7pm6vuiE8L3A+DQo8cD6hQDxhIGhyZWY9Imh0 dHA6Ly93d3cuaXZpZGVvLmNvbXR3L2ZsYXNoL3JvbWFuY2UuYXNwIj4NCjxvYmplY3QgY2xhc3Np ZD0iY2xzaWQ6RDI3Q0RCNkUtQUU2RC0xMWNmLTk2QjgtNDQ0NTUzNTQwMDAwIiBjb2RlQmFzZT0i aHR0cDovL2Rvd25sb2FkLm1hY3JvbWVkaWEuY29tL3B1Yi9zaG9ja3dhdmUvY2Ficy9mbGFzaC9z d2ZsYXNoLmNhYiN2ZXJzaW9uPTQsMCwyLDAiIGhlaWdodD0iMzI0IiB3aWR0aD0iNTUwIj4NCiAg PHBhcmFtIG5hbWU9Il9jeCIgdmFsdWU9IjE0NTUyIj4NCiAgPHBhcmFtIG5hbWU9Il9jeSIgdmFs dWU9Ijg1NzMiPg0KICA8cGFyYW0gbmFtZT0iTW92aWUiIHZhbHVlPSJodHRwOi8vd3d3Lml2aWRl by5jb20udHcvZmxhc2gvY2FyZF8zLnN3ZiI+DQogIDxwYXJhbSBuYW1lPSJTcmMiIHZhbHVlPSJo dHRwOi8vd3d3Lml2aWRlby5jb20udHcvZmxhc2gvY2FyZF8zLnN3ZiI+DQogIDxwYXJhbSBuYW1l PSJXTW9kZSIgdmFsdWU9IldpbmRvdyI+DQogIDxwYXJhbSBuYW1lPSJQbGF5IiB2YWx1ZT0iMCI+ DQogIDxwYXJhbSBuYW1lPSJMb29wIiB2YWx1ZT0iLTEiPg0KICA8cGFyYW0gbmFtZT0iUXVhbGl0 eSIgdmFsdWU9IkhpZ2giPg0KICA8cGFyYW0gbmFtZT0iU0FsaWduIiB2YWx1ZT4NCiAgPHBhcmFt IG5hbWU9Ik1lbnUiIHZhbHVlPSItMSI+DQogIDxwYXJhbSBuYW1lPSJCYXNlIiB2YWx1ZT4NCiAg PHBhcmFtIG5hbWU9IlNjYWxlIiB2YWx1ZT0iU2hvd0FsbCI+DQogIDxwYXJhbSBuYW1lPSJEZXZp Y2VGb250IiB2YWx1ZT0iMCI+DQogIDxwYXJhbSBuYW1lPSJFbWJlZE1vdmllIiB2YWx1ZT0iMCI+ DQogIDxwYXJhbSBuYW1lPSJCR0NvbG9yIiB2YWx1ZT4NCiAgPHBhcmFtIG5hbWU9IlNXUmVtb3Rl IiB2YWx1ZT4NCiAgPHBhcmFtIG5hbWU9IlN0YWNraW5nIiB2YWx1ZT0iYmVsb3ciPjxlbWJlZCBz cmM9Imh0dHA6Ly93d3cuaXZpZGVvLmNvbS50dy9mbGFzaC9jYXJkXzMuc3dmIiBxdWFsaXR5PSJo aWdoIiBwbHVnaW5zcGFnZT0iaHR0cDovL3d3dy5tYWNyb21lZGlhLmNvbS9zaG9ja3dhdmUvZG93 bmxvYWQvaW5kZXguY2dpP1AxX1Byb2RfVmVyc2lvbj1TaG9ja3dhdmVGbGFzaCIgdHlwZT0iYXBw bGljYXRpb24veC1zaG9ja3dhdmUtZmxhc2giIHdpZHRoPSI1NTAiIGhlaWdodD0iMzI0Ij4NCjwv b2JqZWN0Pg0KPC9hPg0KPC9wPg0KDQo8L2JvZHk+DQoNCjwvaHRtbD4= ------=_NextPart_voYwEjHS1D0UbB2hqMCbY2AAA-- ------=_NextPart_voYwEjHS1D0UbB2hqMCbY2A-- From owner-pilc@grc.nasa.gov Tue Feb 12 18:06:57 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00312 for ; Tue, 12 Feb 2002 18:06:56 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 3FBC364150 for ; Tue, 12 Feb 2002 18:05:26 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id RAA06567 for pilc-outgoing; Tue, 12 Feb 2002 17:56:36 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id RAA06551 for ; Tue, 12 Feb 2002 17:56:34 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id RAA02194 for ; Tue, 12 Feb 2002 17:56:33 -0500 (EST) Received: from relay3.kornet.net (unknown [211.48.62.163]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 75CF7C68F5 for ; Tue, 12 Feb 2002 17:56:31 -0500 (EST) Received: from vivi-41a7ime526 (211.227.93.162) by relay3.kornet.net; 13 Feb 2002 07:56:26 +0900 Message-ID: <3c699d9a3c6ad866@relay3.kornet.net> (added by relay3.kornet.net) From: =?ks_c_5601-1987?B?VklWSSBLT1JFQQ==?= To: pilc@grc.nasa.gov Subject: =?ks_c_5601-1987?B?W7GksO1dIHBpbGO01CCwobG4sPjA5b+hvK0gxq+6sMfSwM6wobfOILDtsd67/ciwsKGxuLimILq4s7u15biztM+02S4=?= Date: Wed, 13 Feb 2002 07:56:11 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0077_01C0F56A.93A11C00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-pilc@grc.nasa.gov Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0077_01C0F56A.93A11C00 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 vsiz58fPvLy/5C4NCg0KsKGxuMD8ua6+98O8ILrxuvHE2riuvsYgwNS0z7TZLg0KDQqw7bHe ILv9yLCwobG4uKYgvsbB1iDA+rfFx9EgsKGw3cC4t84gxvfDtSCwobG4sPi03L+hvK0gwffB oiDGx7jFx9W0z7TZLg0KDQrA5bfVLCC87sbELCDEp7Trte4gMjAwMrPiILq9wMcgw9a9xbjw tai3ziC18MDawM7AzLOqIMDnwfq46b+hvK0NCr/svPbH0SDBpsewwLsgvLHBpMfPv6kgxse4 xcfPsO0gwNa9wLTPtNkuDQoNCrHiwbggsKGxuMGhwMcgNDAlfjYwJcGktbUgwPq3xcfPsNQg xse4xcfPsO0gwNa+xr/AtM8NCrLAIMfRufggyKjG5MDMwfa4piC6uL3DseIgudm2+LTPtNku DQoNCrChsbiwoSDHyr/kx8+9w7jpILChsbjA/LmusKHAziDA+sjxv80gwMez7cfYIMHWvcq9 w7/AIA0KQS9TILimILrxt9THz7+pILy6vcfH0SDA2ry8t84gw9a8scC7ILTZIMfPsNq9wLTP tNkuDQoNCmh0dHA6Ly93d3cudml2aS5jby5rci8NCg0KtOe757TCILHNu+cox88pv6EgsPzH z7+pIL7Guau3sSDBpLq4tbUgsK6w7SDA1sH2vsq9wLTPtNkuDQq02bi4IMDMuN7AzyDA2rW/ w9/D4rHit84gwMy43sDPuLggwKW758DMxq6/obytIMPfw+LHz7+0vcC0z7TZDQq89r3FsMW6 ziDHz73HutDAuiC/qbHiIGh0dHA6Ly93d3cuY3J1c2FkZS5jby5rci9yZWplY3QvcmVqZWN0 LnBocD9pZD0yMjQxJmF1dGg9YjZlMzIzMjBmYTZiYzVhNTg4YjkwMTgzYjk1ZGMwMjgmbWFp bD1waWxjQGdyYy5uYXNhLmdvdiZtb2RlPXdyaXRlILimIMWsuK/H2CDB1r3KvcO/wC4NCg0K ------=_NextPart_000_0077_01C0F56A.93A11C00 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 vsiz58fPvLy/5C4NCg0KsKGxuMD8ua6+98O8ILrxuvHE2riuvsYgwNS0z7TZLg0KDQqw7bHe ILv9yLCwobG4uKYgvsbB1iDA+rfFx9EgsKGw3cC4t84gxvfDtSCwobG4sPi03L+hvK0gwffB oiDGx7jFx9W0z7TZLg0KDQrA5bfVLCC87sbELCDEp7Trte4gMjAwMrPiILq9wMcgw9a9xbjw tai3ziC18MDawM7AzLOqIMDnwfq46b+hvK0NCr/svPbH0SDBpsewwLsgvLHBpMfPv6kgxse4 xcfPsO0gwNa9wLTPtNkuDQoNCrHiwbggsKGxuMGhwMcgNDAlfjYwJcGktbUgwPq3xcfPsNQg xse4xcfPsO0gwNa+xr/AtM8NCrLAIMfRufggyKjG5MDMwfa4piC6uL3DseIgudm2+LTPtNku DQoNCrChsbiwoSDHyr/kx8+9w7jpILChsbjA/LmusKHAziDA+sjxv80gwMez7cfYIMHWvcq9 w7/AIA0KQS9TILimILrxt9THz7+pILy6vcfH0SDA2ry8t84gw9a8scC7ILTZIMfPsNq9wLTP tNkuDQoNCmh0dHA6Ly93d3cudml2aS5jby5rci8NCg0KtOe757TCILHNu+cox88pv6EgsPzH z7+pIL7Guau3sSDBpLq4tbUgsK6w7SDA1sH2vsq9wLTPtNkuDQq02bi4IMDMuN7AzyDA2rW/ w9/D4rHit84gwMy43sDPuLggwKW758DMxq6/obytIMPfw+LHz7+0vcC0z7TZDQq89r3FsMW6 ziDHz73HutDAuiC/qbHiIGh0dHA6Ly93d3cuY3J1c2FkZS5jby5rci9yZWplY3QvcmVqZWN0 LnBocD9pZD0yMjQxJmF1dGg9YjZlMzIzMjBmYTZiYzVhNTg4YjkwMTgzYjk1ZGMwMjgmbWFp bD1waWxjQGdyYy5uYXNhLmdvdiZtb2RlPXdyaXRlILimIMWsuK/H2CDB1r3KvcO/wC4NCg0K ------=_NextPart_000_0077_01C0F56A.93A11C00-- From owner-pilc@grc.nasa.gov Wed Feb 13 18:00:38 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23669 for ; Wed, 13 Feb 2002 18:00:38 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 501F4C69A0 for ; Wed, 13 Feb 2002 17:58:40 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id RAA20017 for pilc-outgoing; Wed, 13 Feb 2002 17:47:59 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id RAA20013 for ; Wed, 13 Feb 2002 17:47:58 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id RAA06218 for ; Wed, 13 Feb 2002 17:47:57 -0500 (EST) Received: from novelity.actionweb.net (ns1.dataraze.net [63.69.16.254]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id B26916408F for ; Wed, 13 Feb 2002 17:47:51 -0500 (EST) Received: from ns.actionweb.net ([65.213.155.35]) by novelity.actionweb.net (8.8.5/8.8.8) with SMTP id RAA02295 for ; Wed, 13 Feb 2002 17:27:07 -0500 (EST) From: "info@ergoreal.com" Date: Wed, 13 Feb 2002 17:10:31 To: pilc@grc.nasa.gov Subject: ergoreal. MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_XXWJNAWOLX" Content-Transfer-Encoding: 7bit Message-ID: PM20005:10:31 PM Sender: owner-pilc@grc.nasa.gov Precedence: bulk This is an HTML email message. If you see this, your mail client does not support HTML messages. ------=_NextPart_XXWJNAWOLX Content-Type: text/html;charset="iso-8859-1" Content-Transfer-Encoding: 7bit Untitled Document

 

 

ERGO REAL IS THE MARKETING DIVISION OF TRUE ARM INC.

DIFFERENT COMPANIES HAVE AFFILIATED WITH US

TO DISTRIBUTE OUR SUCCESSFUL AND UNIQUE PRODUCTS.

ALL OF OUR AFFILIATED COMPANIES RECEIVE VERY SUBSTANTIAL COMMISSIONS

SELLING AND MARKETING OUR PRODUCTS.

BECOME ONE OF OUR AFFILIATES AND ENTER INTO THIS NEW WORLD OF OPPORTUNITIES

TO SELL A UNIQUE PATENTED PRODUCT THAT IS USED BY MILLIONS OF PEOPLE.

PLEASE CONTACT US AT:

www.ergoreal.com

 

 

 

 

 

 

 

 

 

We strongly oppose the use of SPAM email and do not want anyone who does not wish to receive our mailings to receive them.
As a result, we have retained the services of an independent 3rd party to administer our list management and remove list. This is not SPAM.
If you do not wish to receive further mailings, please click remove and enter your email at the top of the page.
You may then rest-assured that you will never receive another email from us again.

------=_NextPart_XXWJNAWOLX-- From owner-pilc@grc.nasa.gov Thu Feb 14 15:57:23 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09470 for ; Thu, 14 Feb 2002 15:57:22 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 22CEBC6970 for ; Thu, 14 Feb 2002 15:53:46 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id PAA12900 for pilc-outgoing; Thu, 14 Feb 2002 15:38:55 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id PAA12896 for ; Thu, 14 Feb 2002 15:38:54 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id PAA15235 for ; Thu, 14 Feb 2002 15:38:53 -0500 (EST) Received: from apollo.NORTHLAND.local (unknown [206.47.172.148]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 8833E640E6 for ; Thu, 14 Feb 2002 15:34:32 -0500 (EST) Received: from adaly ([10.1.1.170]) by apollo.NORTHLAND.local with Microsoft SMTPSVC(5.0.2195.3779); Thu, 14 Feb 2002 15:33:35 -0500 Message-ID: <07c801c1b596$dee424e0$aa01010a@northland.local> From: "Alan Daly" To: "Alan Daly" Subject: 2 DAY MPLS COURSE COMING TO OTTAWA, CANADA MARCH 21ST AND 22ND, 2002 Date: Thu, 14 Feb 2002 15:33:29 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_07C5_01C1B56C.F40EF180" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 14 Feb 2002 20:33:35.0645 (UTC) FILETIME=[E054A4D0:01C1B596] Sender: owner-pilc@grc.nasa.gov Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_07C5_01C1B56C.F40EF180 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Please note that this is a one-time mailing only concerning this course = and date. To be removed, simply reply with an "UNSUBSCRIBE" in the body = of the email. Good afternoon Networking Professionals. Northland Systems, the world leader in = non-vendor specific MPLS, Fiber Optic, Gigabit Ethernet, and IP = training, is pleased to announce that our much anticipated, highly = successful, 2 day MPLS Technologies course is scheduled to run again in = Ottawa, Canada on March 21st and 22nd. I was wondering if you could = forward this onto your colleagues and clients to see if they would be = interested in attending. The cost to attend this course is $1100.00 = CDN per student (plus applicable taxes). Taught onsite at such industry = leaders as Alcatel, 360 Networks, Telus, AT&T and Marconi = Communications, the student will leave with a thorough and comprehensive = understanding of this leading-edge networking technology. The class is = limited to 20 students, and we are expecting this session to sell out = extremely quickly, so time is of the essence if you plan on registering = either yourself and/or your colleagues on this course.=20 **PLEASE NOTE THAT AS A SPECIAL OFFER, ANYONE SIGNING UP MORE THAN ONE = ATTENDEE ON THIS COURSE WITH ME AT A TIME WILL RECEIVE A COMPLIMENTARY = NORTHLAND DENIM SHIRT FOR THEMSELVES AS WELL AS THEIR COLLEAGUE(S)!!!** As an added value, all attendees will receive 30 days free access to the = Northland Online "MPLS Technology" eLearning course upon completion of = this session! This course introduces the challenge of the = next generation networks and describes how MPLS addresses it at both a = high and low level. Participants are expected to have a strong = understanding and experience in WANs, LANs, data communications, = routing, internetworking, and communications protocols. This course will: a.. Explain the MPLS concepts, architecture & components.=20 b.. Provide an in-depth view of MPLS.=20 c.. Provide a thorough understanding across all areas of the = technology.=20 d.. Describe how MPLS relates to different evolving network = technologies. Please review the detailed course outline below for more information on = the content being covered. To find out more about how to bring this or any other 2 day course = in-house to a group at your facility, or to register, please call me = directly at 613-667-5063.=20 Have a great day!=20 Sincerely, Alan P. Daly Account Representative Northland Systems Training Inc. 255 Albert St. 5th Floor Ottawa, ON K1P-6A9 Direct: (613) 667-5063 Cellular: (613) 223-1062 Fax: (613) 667-5098 Check Out Our Website at http://www.northlandelearning.com -------------------------------------------------------------------------= --- "Changing learning from an event to a life long process" KNOW YOUR WAY visit http://www.northlandelearning.com -------------------------------------------------------------------------= --- COURSE OUTLINE: *********************** INTRODUCTION=20 =B7 Why MPLS =B7 Routers & Switches =B7 Route at Edge, Switch in Core =B7 Labeled Packet Forwarding =B7 Label & FEC =B7 Traffic Aggregation or Splitting =B7 Label Switched Path =B7 LSP and the Node =B7 LSP Establishment =B7 Packet Labeling & Forwarding =B7 Forwarding Table & LIB =B7 FEC, Labels & LSPs =20 MPLS LABEL ENCODING=20 =B7 Shim Layer Concept =B7 Layer 2 technologies & Labels =B7 MPLS Shim Description =B7 Shim Fields (Label, Exp, S & TTL) =B7 Label Values =B7 Media Encapsulation =B7 Hop Popping =B7 Routing & Tunneling =B7 Multipoint to point trees =B7 MPLS reflects nature of IP Networks =B7 Label Aggregation & Frame merging =B7 Overview: What is MPLS? =20 ICMP MESSAGES=20 =B7 A brief review of ICMP =B7 ICMP Message to source LSR =B7 Tunneling through an AS =B7 Tunnel Private Address via Public Backbones =B7 Extended ICMP Message Length =B7 MPLS Extension Data Structure =B7 MPLS Object Extensions =B7 Stack Entry Object & Extended payload Object =B7 Traceroute over MPLS =20 LDP SIGNALING PROTOCOL=20 =B7 LDP Overview =B7 Applicability & Features =B7 Scalability & Security =B7 LSP Establishment =B7 Upstream LSR versus Downstream LSR =B7 Downstream or Upstream Label Binding =B7 Unsolicited versus On-Demand =B7 Independent or Ordered =B7 Conservative or Liberal Label Retention =B7 Label Request Procedures =B7 L DP over TCP between Neighbors =B7 LDP Security & Privacy =B7 LDP Message Format & Types =B7 For further study items =B7 LDP Message Format & Types =B7 Hello Messages & Targeted Hellos =B7 Encoding of Hello Message & TLVs =B7 Common & Optional Hello Parameters =B7 Hello Discovery Phase =B7 TCP Connection Phases =B7 Session Initialization State Machine =B7 Session Initialization Message =B7 Frame Relay Session Parameters =B7 Advertisement Messages to set LSP =B7 Label Request & Mapping Messages =B7 Label Abort, Withdraw & Release Messages =B7 Address & Address Withdraw Messages =B7 Vendor Private Messages =B7 Notification & Keep Alive Messages =B7 Detailed TLV Encoding =20 CR-LDP SIGNALING PROTOCOL=20 =B7 CR-LDP Overview =B7 Constraint-Routing =B7 CR-LDP Features =B7 Traffic Parameters =B7 Strict & Loose Explicit Routing =B7 Explicit Route TLV =B7 Node & Abstract Node =B7 CSPF =B7 Preemption =B7 Route Pinning =B7 Handling of Failures =B7 LSPID =B7 Resource Class =B7 CR-LDP Messages =B7 LDP PDUs =B7 CR-LDP Message Format =B7 Label Request & Mapping Messages =B7 Notification Message =B7 Detailed CR-LDP TLV Encoding =20 RSVP-TE SIGNALING PROTOCOL=20 =B7 Review of RSVP =B7 RSVP Node & Session Data Flow =B7 Reservation Styles =B7 RSVP PATH & RESV Messages =B7 Reservation & Data Flow =B7 PATH Message & RESV Messages =B7 RSVP Message Common Header =B7 RSVP Message Object Structure =B7 RSVP Message Objects =B7 RSVP-TE Common Header =B7 RSVP-TE Message Object Structure =B7 RSVP-TE LSP Setup Flow =B7 New RSVP-TE Objects =B7 New C-types =B7 RSVP-TE Label Request & Label Objects =B7 LSP Tunnel IP Session Object =B7 ERO & RRO Objects =B7 Path Additional Data Objects =B7 RSVP-TE versus CR-LDP =B7 Comparative Analysis =20 BGP 4=20 =B7 A brief Review on BGP4 =B7 Routing & Tunneling =B7 Directly connected LSRs =B7 Not-directly connected BGP LSRs MPLS over ATM=20 =B7 A brief review of ATM =B7 Motivation for MPLS over ATM =B7 ATM-LSR (LC-ATM, LSR-CC, ATM-CC) =B7 ATM-LSR Behavior & Constraints =B7 Frame-based & Cell-based LSRs =B7 ATM-LSR Integrated & Peer Approaches =B7 SIN Model - Ships in the Night =B7 Transparent Point-to-Point Link =B7 RFC 2684/1483 =B7 Connected through a VP or a VC =B7 VCID & VCID Signaling =B7 ATM Label Stack Encoding =B7 Passing SHIM fields across ATM =B7 VC Merge & Non-VC Merge ATM-LSRs =B7 Communication from edge to edge LSRs =20 VIRTUAL PRIVATE NETWORKS=20 =B7 A brief review on VPN =B7 VPN Overlay & Peer Models =B7 VPN Peer Model Key Technologies =B7 Constrained Distribution of Routing =B7 Extended Communities =B7 PE Forwarding Tables =B7 VPN-IP Address =B7 BGP in PE, IGP within the Provider Network =B7 MPLS as the forwarding Mechanism =20 MPLS QoS SUPPORT=20 =B7 A brief review on IP QoS =B7 IntServ QoS Model =B7 Guaranteed Service & Controlled Load =B7 MPLS RSVP-TE Support of InServ QoS =B7 Diff-Serv QoS Model =B7 MPLS Support of Diff-Serv =B7 E-LSP & L-LSP =B7 MPLS ECN Support =20 MPLS EVOLUTION & REFERENCES=20 =B7 IP Switching Initiatives =B7 MPLS Forum =B7 IETF Working Group MPLS Charter =B7 MPLS Drafts & Standards =B7 MPLS Vendor Products =B7 MPLS Testing & Analyser Products =B7 Interoperability Testing Centers =B7 Example of interoperability testing =B7 MPLS Resource Center =B7 MPLS Applications & Early Adopters =B7 Evolution of the Internet =B7 Convergence of Audio, Video & Data =B7 Next Generation Applications =B7 Abilene & vBNS NGI Initiatives =B7 CA*net 2 & 3 =B7 Next Generation Networks Key Technologies =20 ------=_NextPart_000_07C5_01C1B56C.F40EF180 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Please note that this is a = one-time mailing=20 only concerning this course and date. To be removed, simply reply with = an=20 "UNSUBSCRIBE" in the body of the email.
 
Good afternoon Networking=20 Professionals.
 
          &nbs= p;            = ;     =20 Northland Systems, the world leader in non-vendor specific = MPLS, Fiber=20 Optic, Gigabit Ethernet, and  IP training,  is pleased to = announce that our much anticipated, highly successful, 2 = day MPLS=20 Technologies course is scheduled to run again in Ottawa, Canada = on March 21st and 22nd. I was wondering if = you could=20 forward this onto your colleagues and clients to see if they would be = interested=20 in attending.
 
          &nbs= p;            = ;    =20 The cost to attend this course is $1100.00 CDN per student (plus = applicable=20 taxes). Taught onsite at such industry leaders as = Alcatel, 360=20 Networks, Telus, AT&T and Marconi Communications, the=20 student will leave with a thorough and comprehensive understanding = of this=20 leading-edge networking technology.  The class is limited to = 20=20 students, and we are expecting this session to sell out extremely = quickly, so=20 time is of the essence if you plan on registering either yourself and/or = your=20 colleagues on this course.
 
**PLEASE NOTE THAT AS A SPECIAL OFFER, = ANYONE=20 SIGNING UP MORE THAN ONE ATTENDEE ON THIS COURSE WITH ME AT A TIME WILL = RECEIVE=20 A COMPLIMENTARY NORTHLAND DENIM SHIRT FOR THEMSELVES AS WELL AS THEIR=20 COLLEAGUE(S)!!!**
 
As an added value, all attendees will receive 30 days free = access=20 to the Northland Online "MPLS Technology" eLearning course upon = completion of=20 this session!
 
  =20             &= nbsp;          =20 This course introduces the = challenge of the=20 next generation networks and describes how MPLS addresses it at both a = high and=20 low level. Participants are expected to have a strong understanding = and=20 experience in WANs, LANs, data communications, routing, internetworking, = and=20 communications protocols.
 
This course will:
  • Explain the MPLS concepts, architecture & components.=20
  • Provide an in-depth view of MPLS.=20
  • Provide a thorough understanding across all areas of the = technology.=20
  • Describe how MPLS relates to different evolving network=20 technologies.
Please review the detailed course = outline below for=20 more information on the content being covered.
 
To find out more about how to bring this = or any=20 other 2 day course in-house to a group at your facility, or to register, = please=20 call me directly at 613-667-5063.
 
Have a great day!
 
Sincerely,
 

Alan P. Daly
Account Representative
Northland Systems = Training=20 Inc.
255 Albert St. 5th Floor
Ottawa,=20 ON
K1P-6A9
Direct:     (613)=20 667-5063
Cellular:   (613)=20 223-1062
Fax:        (613)=20 667-5098
Check Out Our Website at http://www.northlandelearning.= com
 
--------------------------------------------------------------------= --------
"Changing=20 learning from an event to a life long process"
 
           &n= bsp;           &nb= sp;  =20 KNOW YOUR=20 WAY
           = visit=20 http://www.northlandelearning.= com
--------------------------------------------------------------= --------------
 
COURSE = OUTLINE:
***********************
 
INTRODUCTION 
=B7    &n= bsp;    =20 Why MPLS
=B7          = Routers=20 & = Switches
=B7          = Route=20 at Edge, Switch in=20 Core
=B7          = Labeled Packet=20 Forwarding
=B7          = Label=20 & FEC
=B7          = Traffic=20 Aggregation or=20 Splitting
=B7          = Label=20 Switched = Path
=B7          LSP = and=20 the Node
=B7          = LSP=20 Establishment
=B7         = ; Packet=20 Labeling &=20 Forwarding
=B7          = Forwarding=20 Table & = LIB
=B7          FEC,=20 Labels & LSPs
 
MPLS LABEL=20 ENCODING 
=B7       &= nbsp; =20 Shim Layer = Concept
=B7         =20 Layer 2 technologies &=20 Labels
=B7          MPLS = Shim=20 Description
=B7          = Shim=20 Fields (Label, Exp, S &=20 TTL)
=B7          Label=20 Values
=B7          = Media=20 Encapsulation
=B7         = ; Hop=20 Popping
=B7          = Routing &=20 Tunneling
=B7          = Multipoint=20 to point = trees
=B7          MPLS=20 reflects nature of IP=20 Networks
=B7          = Label=20 Aggregation & Frame=20 merging
=B7          = Overview:=20 What is MPLS?
 
ICMP=20 MESSAGES 
=B7       &= nbsp; =20 A brief review of=20 ICMP
=B7          ICMP = Message to=20 source LSR
=B7          = Tunneling=20 through an = AS
=B7          Tunnel=20 Private Address via Public=20 Backbones
=B7          = Extended=20 ICMP Message = Length
=B7         =20 MPLS Extension Data=20 Structure
=B7          = MPLS Object=20 Extensions
=B7          = Stack=20 Entry Object & Extended payload=20 Object
=B7          = Traceroute=20 over MPLS
 
LDP SIGNALING=20 PROTOCOL 
=B7       &= nbsp; =20 LDP = Overview
=B7         =20 Applicability &=20 Features
=B7          = Scalability=20 & = Security
=B7          = LSP=20 Establishment
=B7         = ;=20 Upstream LSR versus Downstream=20 LSR
=B7          = Downstream or=20 Upstream Label=20 Binding
=B7          = Unsolicited=20 versus = On-Demand
=B7         =20 Independent or=20 Ordered
=B7          = Conservative=20 or Liberal Label=20 Retention
=B7          = Label=20 Request = Procedures
=B7          = L=20 DP over TCP between=20 Neighbors
=B7          = LDP=20 Security &=20 Privacy
=B7          LDP = Message=20 Format & = Types
=B7         =20 For further study=20 items
=B7          LDP = Message=20 Format & = Types
=B7         =20 Hello Messages & Targeted=20 Hellos
=B7          = Encoding of=20 Hello Message &=20 TLVs
=B7          Common = &=20 Optional Hello=20 Parameters
=B7          = Hello=20 Discovery = Phase
 =B7          = TCP Connection = Phases
=B7         =20 Session Initialization State=20 Machine
=B7          = Session=20 Initialization=20 Message
=B7          = Frame Relay=20 Session = Parameters
=B7         =20 Advertisement Messages to set=20 LSP
=B7          Label = Request=20 & Mapping=20 Messages
=B7          = Label Abort,=20 Withdraw & Release=20 Messages
=B7          = Address=20 & Address Withdraw=20 Messages
=B7          = Vendor=20 Private = Messages
=B7         =20 Notification & Keep Alive=20 Messages
=B7          = Detailed TLV=20 Encoding
 
CR-LDP SIGNALING=20 PROTOCOL 
=B7       &= nbsp; =20 CR-LDP = Overview
=B7         =20 Constraint-Routing
=B7        =  =20 CR-LDP = Features
=B7         =20 Traffic = Parameters
=B7         =20 Strict & Loose Explicit=20 Routing
=B7          = Explicit=20 Route TLV
=B7          = Node &=20 Abstract = Node
=B7         =20 CSPF
=B7         =20 Preemption
=B7          = Route=20 Pinning
=B7          = Handling of=20 Failures
=B7         =20 LSPID
=B7          = Resource=20 Class
=B7          = CR-LDP=20 Messages
=B7          = LDP=20 PDUs
=B7          CR-LDP = Message=20 Format
=B7          = Label Request=20 & Mapping=20 Messages
=B7          = Notification=20 Message
=B7          = Detailed=20 CR-LDP TLV Encoding
 
RSVP-TE SIGNALING=20 PROTOCOL 
=B7       &= nbsp; =20 Review of = RSVP
=B7          RSVP=20 Node & Session Data=20 Flow
=B7          = Reservation=20 Styles
=B7          RSVP = PATH=20 & RESV = Messages
=B7         =20 Reservation & Data=20 Flow
=B7          PATH = Message=20 & RESV = Messages
=B7         =20 RSVP Message Common=20 Header
=B7          RSVP = Message=20 Object = Structure
=B7          = RSVP=20 Message = Objects
=B7         =20 RSVP-TE Common = Header
=B7         =20 RSVP-TE Message Object=20 Structure
=B7          = RSVP-TE LSP=20 Setup Flow
=B7          = New=20 RSVP-TE = Objects
=B7          New = C-types
=B7          = RSVP-TE Label=20 Request & Label=20 Objects
=B7          LSP = Tunnel IP=20 Session = Object
=B7          ERO=20 & RRO = Objects
=B7         =20 Path Additional Data=20 Objects
=B7          = RSVP-TE=20 versus = CR-LDP
=B7         =20 Comparative Analysis
 
BGP=20 4 
=B7        &n= bsp; A=20 brief Review on = BGP4
=B7         =20 Routing &=20 Tunneling
=B7          = Directly=20 connected = LSRs
=B7         =20 Not-directly connected BGP LSRs
 
MPLS over=20 ATM 
=B7        =   A=20 brief review of = ATM
=B7         =20 Motivation for MPLS over=20 ATM
=B7          ATM-LSR = (LC-ATM,=20 LSR-CC, = ATM-CC)
=B7         =20 ATM-LSR Behavior &=20 Constraints
=B7          = Frame-based & Cell-based=20 LSRs
=B7          = ATM-LSR=20 Integrated & Peer=20 Approaches
=B7          = SIN Model=20 - Ships in the = Night
=B7         =20 Transparent Point-to-Point=20 Link
=B7          RFC=20 2684/1483
=B7          = Connected=20 through a VP or a = VC
=B7         =20 VCID & VCID=20 Signaling
=B7          = ATM Label=20 Stack = Encoding
=B7         =20 Passing SHIM fields across=20 ATM
=B7          VC = Merge &=20 Non-VC Merge = ATM-LSRs
=B7         =20 Communication from edge to edge LSRs
 
VIRTUAL = PRIVATE=20 NETWORKS 
=B7       &= nbsp; =20 A brief review on = VPN
=B7         =20 VPN Overlay & Peer=20 Models
=B7          VPN = Peer Model=20 Key = Technologies
=B7         = =20 Constrained Distribution of=20 Routing
=B7          = Extended=20 Communities
=B7          = PE=20 Forwarding = Tables
=B7         =20 VPN-IP = Address
=B7          BGP = in=20 PE, IGP within the Provider=20 Network
=B7          = MPLS as the=20 forwarding Mechanism
 
MPLS QoS=20 SUPPORT 
=B7       &n= bsp; =20 A brief review on IP=20 QoS
=B7          IntServ = QoS=20 Model
=B7          = Guaranteed=20 Service & Controlled=20 Load
=B7          MPLS = RSVP-TE=20 Support of  InServ=20 QoS
=B7          = Diff-Serv QoS=20 Model
=B7          MPLS = Support of=20 Diff-Serv
=B7          = E-LSP &=20 L-LSP
=B7          MPLS = ECN=20 Support
 
MPLS EVOLUTION &=20 REFERENCES 
=B7       = ;  =20 IP Switching=20 Initiatives
=B7          = MPLS=20 Forum
=B7          IETF = Working=20 Group MPLS = Charter
=B7         =20 MPLS Drafts &=20 Standards
=B7          = MPLS Vendor=20 Products
=B7          = MPLS Testing=20 & Analyser=20 Products
=B7         =20 Interoperability Testing=20 Centers
=B7          = Example of=20 interoperability=20 testing
=B7          = MPLS Resource=20 Center
=B7          MPLS = Applications & Early=20 Adopters
=B7          = Evolution of=20 the = Internet
=B7         =20 Convergence of Audio, Video &=20 Data
=B7          Next = Generation=20 Applications
=B7         = Abilene=20 & vBNS NGI=20 Initiatives
=B7          = CA*net 2=20 & 3
=B7          = Next=20 Generation Networks Key Technologies
 
 =20
 
------=_NextPart_000_07C5_01C1B56C.F40EF180-- From owner-pilc@grc.nasa.gov Fri Feb 15 13:14:37 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14541 for ; Fri, 15 Feb 2002 13:14:36 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id C8EBB64162 for ; Fri, 15 Feb 2002 13:11:56 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id NAA13658 for pilc-outgoing; Fri, 15 Feb 2002 13:04:53 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id NAA13638 for ; Fri, 15 Feb 2002 13:04:52 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id NAA15423 for ; Fri, 15 Feb 2002 13:04:50 -0500 (EST) Received: from localhost (unknown [211.50.255.50]) by seraph3.grc.nasa.gov (Postfix) with SMTP id 3B9076411B for ; Fri, 15 Feb 2002 13:03:53 -0500 (EST) Reply-To: pricelist@hutmail.com From: ÄÄÁ¤º¸ To: pilc@grc.nasa.gov Subject: {±¤ °í} ÄÄÇ»ÅͰ¡°ÝÁ¤º¸ ¸ÞÀϸµ ȸ¿øÀÌ µÇ¼¼¿ä (^-^)~ Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Sat, 16 Feb 2002 03:03:53 +0900 Message-Id: <20020215180353.3B9076411B@seraph3.grc.nasa.gov> Sender: owner-pilc@grc.nasa.gov Precedence: bulk ÄÄÇ»ÅÍ °¡°ÝÁ¤º¸ ¸ÞÀϸµ ½Åû ¹Þ½À´Ï´Ù.

¸ÕÀú Çã¶ô¾øÀÌ ±ÛÀ» ¿Ã¸°°Í¿¡ ´ëÇØ Áø½ÉÀ¸·Î »ç°ú¸»¾¸ µå¸³´Ï´Ù.
±ÍÇÏÀÇ À̸ÞÀÏ ÁÖ¼Ò´Â ÀÎÅÍ³Ý °Ô½ÃÆÇÀ» ÅëÇÏ¿© ÃëÇÕÇÏ¿´½À´Ï´Ù

ÄÄÇ»ÅÍ °¡°ÝÁ¤º¸¸¦
¸ÅÀÏ ¸ÅÀÏ È¸¿ø´ÔÀÇ À̸ÞÀÏ·Î ¹ß¼ÛÇØ µå¸®´Â ¼­ºñ½ºÀÔ´Ï´Ù.
Ç×»ó ÃÖ½ÅÀÇ °¡°ÝÁ¤º¸°¡ ȸ¿ø´ÔÀÇ À̸ÞÀϼӿ¡ ´ã°ÜÁ® ÀÖ°Ô ÇØµå¸®°Ú½À´Ï´Ù.

ÇöÀç Àϰ£(È­,¸ñ,Åä¿äÀÏ ¹ßÇà) ¹× ÁÖ°£(¸ñ¿äÀÏ ¹ßÇà) ÇüÅ·Π¹ßÇàÁßÀÔ´Ï´Ù.
ÀÏ¿äÀÏ ¹× °øÈÞÀÏÀº ¹ßÇàÀ» ÇÏÁö ¾Ê½À´Ï´Ù.

¹°·Ð º» ¼­ºñ½º´Â ¹«·áÀÔ´Ï´Ù.

±¸µ¶½ÅûÀº ¸ÞÀÏÁÖ¼Ò¸¸ ½áÁÖ½Ã¸é ³¡ÀÔ´Ï´Ù.. °£´ÜÇÏÁÒ..^^

ÄÄÇ»ÅÍ °¡°ÝÁ¤º¸ [Àϰ£]



ÄÄÇ»ÅÍ °¡°ÝÁ¤º¸ [ÁÖ°£]


ÇѸÞÀÏ »ç¿ëÀÚ¿ë [Àϰ£]
  ÄÄÇ»ÅͰ¡°ÝÁ¤º¸

ÇѸÞÀÏ »ç¿ëÀÚ¿ë [ÁÖ°£]
  ÄÄÇ»ÅͰ¡°ÝÁ¤º¸

Áö³­¸ÞÀϸµº¸±â ¡Ú

º» ¸ÞÀÏ·Î ±âºÐ »óÇÏ¼Ì´Ù¸é ±íÀÌ»ç°ú µå¸³´Ï´Ù.!
¼ö½Å°ÅºÎ ÇØÁÖ½Ã¸é ¹Ýº¹¹ß¼ÛÇÏÁö ¾Êµµ·Ï ÇϰڽÀ´Ï´Ù.
º»¸ÞÀÏÀº 1ȸ¼º ¸ÞÀÏÀÔ´Ï´Ù.

¼ö½Å°ÅºÎ <== ¼ö½Å°ÅºÎ´Â ²À ¿ä±â¸¦ ´­·¯ÁÖ¼¼¿ä.. °¨»çÇÕ´Ï´Ù.

From owner-pilc@grc.nasa.gov Fri Feb 15 21:29:00 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25101 for ; Fri, 15 Feb 2002 21:29:00 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 46FB1640B8 for ; Fri, 15 Feb 2002 21:29:00 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id VAA16381 for pilc-outgoing; Fri, 15 Feb 2002 21:21:13 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id VAA16377 for ; Fri, 15 Feb 2002 21:21:12 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id VAA26275 for ; Fri, 15 Feb 2002 21:21:11 -0500 (EST) Received: by seraph2.grc.nasa.gov (Postfix, from userid 5) id 4A8A4C6934; Fri, 15 Feb 2002 21:20:35 -0500 (EST) Received: from unknown(211.222.117.6) by seraph2.grc.nasa.gov via csmap (V6.0) id srcAAAUMaGFV; Fri, 15 Feb 02 21:20:34 -0500 Reply-To: gtech@gtech21.com From: (ÁÖ) ÁöÅØ To: pilc@grc.nasa.gov Subject: ÀÚµ¿ ÁÙ°¨±èÀåÄ¡ ºÎÂø ½Å°³³ä ÈÞ´ëÆù¿ë À̾îÆù !!! [±¤°í] Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Sat, 16 Feb 2002 11:10:35 +0900 Message-Id: <20020216022035.4A8A4C6934@seraph2.grc.nasa.gov> Sender: owner-pilc@grc.nasa.gov Precedence: bulk mail02-1
¢Á Çã¶ô¾øÀÌ ¸ÞÀÏÀ» º¸³»¼­ Á˼ÛÇÕ´Ï´Ù.
¢Á º»¸ÞÀÏÀº Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀǰÅÇÑ [±¤°í] ¸ÞÀÏÀÔ´Ï´Ù.
¢Á e-mail ÁÖ¼Ò´Â ÀÎÅͳݻ󿡼­ ÃëµæÇÏ¿´À¸¸ç, ÁÖ¼Ò¿Ü ¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö ¾Ê½À´Ï´Ù.
¢Á ¼ö½ÅÀ» ¿øÄ¡ ¾ÊÀ¸½Ã¸é '¼ö½Å°ÅºÎ'¸¦ ´­·¯ÁÖ¼¼¿ä. [¼ö½Å°ÅºÎ]
 
 
 
 
(ÁÖ)ÁöÅØ ÀÎõ±¤¿ª½Ã °è¾ç±¸ ÀÛÀüµ¿ 852-73 Tel:(032)552-7222
E-mail : gtech@gtech21.com    Homepage : http://www.gtech21.com
 
From owner-pilc@grc.nasa.gov Sat Feb 16 23:45:29 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23326 for ; Sat, 16 Feb 2002 23:45:28 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id D80BB640CE for ; Sat, 16 Feb 2002 23:45:30 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id XAA25093 for pilc-outgoing; Sat, 16 Feb 2002 23:38:35 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id XAA25067 for ; Sat, 16 Feb 2002 23:38:34 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id XAA02872 for ; Sat, 16 Feb 2002 23:38:32 -0500 (EST) Received: by seraph2.grc.nasa.gov (Postfix, from userid 5) id 5EEA6C6906; Sat, 16 Feb 2002 23:36:36 -0500 (EST) Received: from unknown(61.98.156.173) by seraph2.grc.nasa.gov via csmap (V6.0) id srcAAAh9aG8x; Sat, 16 Feb 02 23:36:35 -0500 Reply-To: mob1000@lycos.co.kr From: ¹éÁ¤Çö To: pilc@grc.nasa.gov Subject: »ç¿ø¸ðÁý¹×±¸Àα¤°í Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Sun, 17 Feb 2002 13:33:38 +0900 Message-Id: <20020217043636.5EEA6C6906@seraph2.grc.nasa.gov> Sender: owner-pilc@grc.nasa.gov Precedence: bulk

°¥¼ö·Ï ³ô¾ÆÁö´Â °í°´µéÀÇ ´Ù¾çÇϰí ǰ°ÝÀûÀÎ ¿ä±¸¿¡ ºÎÇյǴÂ
Wedding,Tour,Couple,Leisure,Event Manager
Àü¹® À°¼ºÀ» ÅëÇÏ¿© Àü±¹ ±×¸®°í ÇØ¿Ü ½ÃÀå¿¡ µµÀüÇÒ ÀÎÀ縦 ¸ðÁýÇϰí ÀÖ½À´Ï´Ù.
ÁøÃëÀûÀ̰í ÀþÀº »ý°¢°ú ³¢·Î ¶Ê¶Ê¹¶ÃÄÁø ºÐÀ̶ó¸é µµÀüÇϽʽÿä.
ÇÑ ¸íÀÇ ¸Å´ÏÁ®·Î¼­ ±× À§¿¡ ¿ì¶Ò ¼ÚÀº ÇÑ»ç¶÷ÀÇ °æ¿µÀÎÀ¸·Î¼­ °Åµì³¯¼ö ÀÖµµ·Ï
Á¶¾Æ½ºÅ丮º¥Æ®°¡ ÇÔ²² ÇϰڽÀ´Ï´Ù.
¸ðÁýºÎºÐ ¿þµù,Ä¿ÇÃ,À̺¥Æ®,·¹Á®,Åõ¾î¸Å´ÏÁ®
- ¼ö½À»ç¿ø(ÀÎÅÏ) : 5°³ºÎ¹® ±âÃʱ³À°¼ö·á(18½Ã°£),Marketing´É·ÂÃøÁ¤
- »ç¿ø : Àü¹ÝÀûÀÎ Çà»çstep,±âÃʰü¸® ¾÷¹«,Marketing±³À°¼ö·á
- ÆÀÀå : Çà»ç ±âȹ ¹× ÁøÇà,¿¹½Ä»ó´ã,À̺¥Æ® »ç¾÷Àü°³
- CEE.CEO : Á¶Á÷°ü¸®.°æ¿µÀÚ °úÁ¤ À̼ö
- ÇзÂ/Àü°ø : ÃÊ´ëÁ¹ ÀÌ»ó/ºÒ¹®
ä¿ë½Ã±â - ¿¬·É : 21-30¼¼(³²,¿©)³²ÀÚ´Â ±ºÇÊÀÚ.±âÈ¥ÀÚ °¡´É(¸éÁ¢ÈÄ °áÁ¤)
¸ðÁýÀοø ½ÅÀÔ00¸í/°æ·Â00¸í
ÀüÇü¹æ¹ý - 1Â÷ : ¼­·ù½É»ç
- 2Â÷ : ¸éÁ¢(1Â÷ ÇÕ°ÝÀÚ¿¡°Ô °³º° Å뺸)
Á¢¼ö¹æ¹ý ÀüÈ­ ¹× ¿ìÆíÁ¢¼ö ÈÄ ³»»ç
Á¦Ãâ¼­·ù - À̷¼­
- ÀÚ±â¼Ò°³¼­
- Áֹεî·Ï µîº» 1Åë
Á¦ Ãâ ó ´ë±¸±¤¿ª½Ã Áß±¸ ³²»ê 1µ¿ 2109-10¹øÁö
±Ù¹«½Ã°£ ÆòÀÏ 08:30 - 17:30, Åä¿äÀÏ 08:30 - 12:00
*Àλç´ã´çÀÚ : ¹éÁ¤Çö ÆÀÀå
TEL : 053-214-2588
H.P : 016-9797-3599
E- mail : mob1000 @ empal.com

¼ö½Å°ÅºÎÇÕ´Ï´Ù

»ó¾÷¼º ±¤°í¸ÞÀÏÀ» º¸³»°Ô µÇ¾î¼­ Á¤¸»Á˼ÛÇÕ´Ï´Ù
´ÔÀÇ ¸ÞÀÏÁÖ¼Ò´Â ÀÎÅͳݿ©ÇàÀ» ÇÏ´Ù ¼öÁýÇÏ¿´À¾´Ï´Ù.
ÀúÈñ´Â ±ÍÇÏ¿¡ ´ëÇØ ¾î¶°ÇÑ Á¤º¸µµ °¡Áö°íÀÖÁö¾Ê½À´Ï´Ù
¼ö½Å°ÅºÎ¸¦ ÇØÁÖ½Ã¸é ´ÙÀ½ºÎÅÍ´Â µÎ¹ø´Ù½Ã ¸ÞÀÏÀ» º¸³»Áö ¾Ê°Ú½À´Ï´Ù
From owner-pilc@grc.nasa.gov Sun Feb 17 14:19:03 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10192 for ; Sun, 17 Feb 2002 14:19:03 -0500 (EST) Received: by seraph2.grc.nasa.gov (Postfix, from userid 5) id 0A6C2C69D5; Sun, 17 Feb 2002 14:17:50 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov(139.88.112.33) by seraph2.grc.nasa.gov via csmap (V6.0) id srcAAAyQaaUz; Sun, 17 Feb 02 14:17:49 -0500 Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id OAA01596 for pilc-outgoing; Sun, 17 Feb 2002 14:12:11 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id OAA01586 for ; Sun, 17 Feb 2002 14:12:10 -0500 (EST) From: RCPMailing@hotmail.com Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id OAA28020 for ; Sun, 17 Feb 2002 14:12:09 -0500 (EST) Received: from yourwebsite.com (adsl-66-136-202-106.dsl.austtx.swbell.net [66.136.202.106]) by seraph3.grc.nasa.gov (Postfix) with SMTP id 6F633640C4 for ; Sun, 17 Feb 2002 14:11:59 -0500 (EST) Reply-To: RCPMailing@hotmail.com To: pilc@grc.nasa.gov Subject: Receive $2 for every envelope you stuff for our company! Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sun, 17 Feb 2002 13:12:18 -0600 Message-Id: <20020217191159.6F633640C4@seraph3.grc.nasa.gov> Sender: owner-pilc@grc.nasa.gov Precedence: bulk Receive $2 for every envelope you stuff for our company! No experience required! Visit http://www.rcplanet.tv for more information! Regards, RCPM Staff This is a one time e-mail and you will not recieve any more e-mails from us. From owner-pilc@grc.nasa.gov Mon Feb 18 11:25:12 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07262 for ; Mon, 18 Feb 2002 11:25:12 -0500 (EST) Received: by seraph2.grc.nasa.gov (Postfix, from userid 5) id 69082C693F; Mon, 18 Feb 2002 11:25:15 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov(139.88.112.33) by seraph2.grc.nasa.gov via csmap (V6.0) id srcAAAtBaOor; Mon, 18 Feb 02 11:25:15 -0500 Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id LAA17044 for pilc-outgoing; Mon, 18 Feb 2002 11:18:41 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id LAA17038 for ; Mon, 18 Feb 2002 11:18:40 -0500 (EST) From: youcherry@yahoo.com Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id LAA09782 for ; Mon, 18 Feb 2002 11:18:39 -0500 (EST) Received: from yahoo.com (unknown [212.0.216.2]) by seraph3.grc.nasa.gov (Postfix) with SMTP id 3C73C6408D for ; Mon, 18 Feb 2002 11:18:33 -0500 (EST) Reply-To: youcherry@yahoo.com To: pilc@grc.nasa.gov Subject: Take me. Date: 18 Feb 2002 16:50:52 GMT MIME-Version: 1.0 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: 8bit Message-Id: <20020218161833.3C73C6408D@seraph3.grc.nasa.gov> Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 8bit


Can you break my cherry?

Click Here and give it a try...


Little sluts are waiting for your big dick!
What are you waiting for?

HERE

















Note: this is not a spam email. This email was sent to you because your email was entered in on a website requesting to be a registered subscriber. If you did not request this email, please just answer on this mail.


From owner-pilc@grc.nasa.gov Tue Feb 19 07:18:07 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15725 for ; Tue, 19 Feb 2002 07:18:07 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 396A16412E for ; Tue, 19 Feb 2002 07:15:13 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id HAA22372 for pilc-outgoing; Tue, 19 Feb 2002 07:10:20 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id HAA22368 for ; Tue, 19 Feb 2002 07:10:19 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id HAA01511 for ; Tue, 19 Feb 2002 07:10:18 -0500 (EST) Received: by seraph2.grc.nasa.gov (Postfix, from userid 5) id 1795BC68FE; Tue, 19 Feb 2002 07:10:18 -0500 (EST) Received: from odin.ietf.org(132.151.1.176) by seraph2.grc.nasa.gov via csmap (V6.0) id srcAAAsCaq3l; Tue, 19 Feb 02 07:10:17 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15326; Tue, 19 Feb 2002 07:10:15 -0500 (EST) Message-Id: <200202191210.HAA15326@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: pilc@grc.nasa.gov From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-pilc-2.5g3g-06.txt Date: Tue, 19 Feb 2002 07:10:15 -0500 Sender: owner-pilc@grc.nasa.gov Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Performance Implications of Link Characteristics Working Group of the IETF. Title : TCP over 2.5G and 3G Wireless Networks Author(s) : H. Inamura et al. Filename : draft-ietf-pilc-2.5g3g-06.txt Pages : 26 Date : 18-Feb-02 This document describes a profile for optimizing TCP over 2.5G/3G wireless networks. We introduce examples of wireless internet services and standardization activities that potentially will deploy the profile described in this document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pilc-2.5g3g-06.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-pilc-2.5g3g-06.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-pilc-2.5g3g-06.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: <20020218134340.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pilc-2.5g3g-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pilc-2.5g3g-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020218134340.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-pilc@grc.nasa.gov Tue Feb 19 23:32:51 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14415 for ; Tue, 19 Feb 2002 23:32:50 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id B3FFC640C6 for ; Tue, 19 Feb 2002 23:32:52 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id XAA09096 for pilc-outgoing; Tue, 19 Feb 2002 23:23:58 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id XAA09086 for ; Tue, 19 Feb 2002 23:23:57 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id XAA08583 for ; Tue, 19 Feb 2002 23:23:56 -0500 (EST) Received: from lawyers.grc.nasa.gov (d134.as1.clev.oh.voyager.net [209.81.166.135]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 492A9C6933 for ; Tue, 19 Feb 2002 23:23:17 -0500 (EST) Received: from lawyers (mallman@localhost) by lawyers.grc.nasa.gov (8.9.3/8.9.3) with ESMTP id XAA27815 for ; Tue, 19 Feb 2002 23:22:30 -0500 Message-Id: <200202200422.XAA27815@lawyers.grc.nasa.gov> To: pilc@grc.nasa.gov From: Mark Allman Reply-To: mallman@grc.nasa.gov Subject: new rev of LINK Organization: BBN Technologies/NASA GRC Song-of-the-Day: Superunknown Date: Tue, 19 Feb 2002 23:22:30 -0500 Sender: owner-pilc@grc.nasa.gov Precedence: bulk Folks- I just sent the secratariet a new version of LINK. Some notes... * See http://roland.grc.nasa.gov/~mallman/share/link/ for the latest rev, as well as diffs and word diffs since the last version. I also included the last version in that directory as well so that you can use whatever sort of differ you like best. * The author list has been trimmed because the RFC editor is no longer publishing RFCs with more than 5 authors. This seemed like the fairest approach. (Authors -- err, former authors -- have been notified under seperate cover, as well.) * The fixes between this version and the last.... nits all over the place. The CRC section has been overhauled (Gorry and Lloyd). The broadcast and multicast sections have been reworked a little (Gorry) and moved within the document. Finally, I tried to hack at the BoD section a little. * Please check the document to make sure I included your comments. There is a decent chance that I something could have been dropped on the floor in the handoff between Phil and I. * I plan to issue another rev of this document on 3/1 (the deadline for Minneapolis). In the next week and a half people should read the document to make sure it is in good shape and that I have included all the fixes that I am supposed to have included. After 3/1 the chairs will issue another WG last call for the document (likely to be short given that we have already gone through one). And, then it is off to the IESG for this doc. Send heartburn if you've got it. And, quick. Thanks, allman --- Mark Allman -- NASA GRC/BBN -- http://roland.grc.nasa.gov/~mallman/ From owner-pilc@grc.nasa.gov Wed Feb 20 09:30:52 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01620 for ; Wed, 20 Feb 2002 09:30:51 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id B48DBC6940 for ; Wed, 20 Feb 2002 09:30:50 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id JAA05461 for pilc-outgoing; Wed, 20 Feb 2002 09:23:01 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id JAA05451 for ; Wed, 20 Feb 2002 09:23:00 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id JAA05061 for ; Wed, 20 Feb 2002 09:22:57 -0500 (EST) Received: from hatoo.net (unknown [61.101.11.42]) by seraph3.grc.nasa.gov (Postfix) with SMTP id E4702640CD for ; Wed, 20 Feb 2002 09:22:55 -0500 (EST) Message-ID: <415358-22002232014232062@hatoo.net> X-EM-Version: 6, 0, 0, 4 X-EM-Registration: #0010630410721500AB30 Reply-To: "'µµÇÐÀ§·æ'" From: "µµÇÐÀ§·æ" To: pilc@grc.nasa.gov Subject: [±¤°í] ¾Æ½Ã³ª¿ä? ¿ëÀïÈ­Åõ? Date: Wed, 20 Feb 2002 23:23:20 +0900 MIME-Version: 1.0 Content-Type: text/html; charset=euc-kr Sender: owner-pilc@grc.nasa.gov Precedence: bulk
 
 
 
 
¾È³çÇϼ¼¿ä.
¹àÀº ¸¶À½, ¹àÀº È­Åõ, ¿ëÀïÈ­ÅõÀÔ´Ï´Ù.

¿ëÀïÈ­Åõ°¡ ¹¹³Ä±¸¿ä?
¿ëÀïÈ­Åõ´Â µðÀÚÀÎ Àü¹®È¸»ç¿¡¼­ ¸¸µç ij¸¯ÅÍ È­ÅõÀÔ´Ï´Ù.

¸¹Àº ºÐµéÀÌ Áñ±â½ÃÁö¸¸ ºÎÁ¤ÀûÀÎ À̹ÌÁö¸¦ ¸¹ÀÌ ´ã°í ÀÖ´Â ±âÁ¸ÀÇ È­Åõ¸¦
¹à°í ±àÁ¤ÀûÀÎ À̹ÌÁö·Î RedisignÇÑ È­Åõ¶ø´Ï´Ù.

ÀÌÁ¦ À½Ä§ÇÑ ºÐÀ§±âÀÇ È­Åõ´Â ¾È³ç~~~
¸¶À½±îÁö ¹à¾ÆÁö´Â ¿ëÀïÈ­Åõ¸¦ Áñ°Üº¸¼¼¿ä^^




±ÍÇÏÀÇ ½Â¶ô¾øÀÌ È«º¸¼º À̸ÞÀÏÀ» º¸³»°Ô µÈ Á¡ Á¤ÁßÈ÷ »ç°úµå¸³´Ï´Ù.

º»¸ÞÀÏÀº Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø¹ý ±ÔÁ¤À» ÁؼöÇÏ¿© [±¤°í] ¸ÞÀÏÀÓÀ» Ç¥½ÃÇÏ¿´À¸¸ç, ¼ö½Å°ÅºÎ¸¦ ÇÒ¼ö ÀÖµµ·Ï ÇÏ¿´½À´Ï´Ù.

º» ¸ÞÀÏÀº ÀÎÅÍ³Ý »ó¿¡ °ø°³µÈ ¸ÞÀÏ ÁÖ¼Ò¸¦ ±Ù°Å·Î ¹ß¼ÛÇÏ¿´À¸¸ç
±ÍÇÏÀÇ À̸ÞÀÏ Á¤º¸ À̿ܿ¡ ÀúÈñ°¡ º¸À¯Çϰí ÀÖ´Â °³ÀÎÁ¤º¸´Â ÀÏü °®°í ÀÖÁö¾ÊÀ½À» ¾Ë·Áµå¸³´Ï´Ù.

±ÍÇÏÀÇ ÇູÇÑ ³¯°ú ÇϽôÂÀÏ ¸ðµÎ ¹øÃ¢ÇÏ½Ã±æ ¹Ù¶ø´Ï´Ù.
 
 
Copyright(c) 2001 PARL Entertainment Co,.Ltd All right Reserved.
From owner-pilc@grc.nasa.gov Wed Feb 20 12:44:53 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10728 for ; Wed, 20 Feb 2002 12:44:53 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 098F064133 for ; Wed, 20 Feb 2002 12:36:09 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id MAA05195 for pilc-outgoing; Wed, 20 Feb 2002 12:28:47 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id MAA05184 for ; Wed, 20 Feb 2002 12:28:45 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id MAA10874 for ; Wed, 20 Feb 2002 12:28:42 -0500 (EST) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 988F464113 for ; Wed, 20 Feb 2002 12:27:30 -0500 (EST) Received: from nit (nit.isi.edu [128.9.160.116]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g1KHRUQ25467; Wed, 20 Feb 2002 09:27:30 -0800 (PST) Date: Wed, 20 Feb 2002 09:27:29 -0800 From: Aaron Falk To: pilc Cc: Spencer Dawkins , Allison Mankin Subject: pilc not meeting in Minneapolis Message-ID: <1880000.1014226049@nit> X-Mailer: Mulberry/2.1.2 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 7bit Just an FYI. There are no plans to schedule a meeting of PILC in Minneapolis. As far as I can tell, we have no major open issues. The two remaining documents (LINK and 2.5g3g) are stable and will be last called before the meeting. It wouldn't be a good use of IETF resources to schedule a meeting. --aaron From owner-pilc@grc.nasa.gov Thu Feb 21 07:15:39 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14595 for ; Thu, 21 Feb 2002 07:15:38 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id A80F3C694A for ; Thu, 21 Feb 2002 07:14:55 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id HAA11396 for pilc-outgoing; Thu, 21 Feb 2002 07:04:29 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id HAA11383 for ; Thu, 21 Feb 2002 07:04:28 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id HAA29301 for ; Thu, 21 Feb 2002 07:04:26 -0500 (EST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 4233AC693A for ; Thu, 21 Feb 2002 07:02:09 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14209; Thu, 21 Feb 2002 07:02:06 -0500 (EST) Message-Id: <200202211202.HAA14209@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: pilc@grc.nasa.gov From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-pilc-link-design-08.txt Date: Thu, 21 Feb 2002 07:02:06 -0500 Sender: owner-pilc@grc.nasa.gov Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Performance Implications of Link Characteristics Working Group of the IETF. Title : Advice for Internet Subnetwork Designers Author(s) : P. Karn et al. Filename : draft-ietf-pilc-link-design-08.txt Pages : 21 Date : 20-Feb-02 This document provides advice to the designers of digital communication equipment, link layer protocols and packet switched subnetworks (collectively referred to as subnetworks) who wish to support the Internet protocols but who may be unfamiliar with Internet architecture and the implications of their design choices on the performance and efficiency of the Internet. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pilc-link-design-08.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. 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-pilc-link-design-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-pilc-link-design-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: <20020220135225.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-pilc-link-design-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-pilc-link-design-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020220135225.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-pilc@grc.nasa.gov Fri Feb 22 15:14:31 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20476 for ; Fri, 22 Feb 2002 15:14:30 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id A6BFFC6987 for ; Fri, 22 Feb 2002 15:13:42 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id PAA15563 for pilc-outgoing; Fri, 22 Feb 2002 15:01:24 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id PAA15559; Fri, 22 Feb 2002 15:01:23 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id PAA26064; Fri, 22 Feb 2002 15:01:22 -0500 (EST) Received: from motgate4.mot.com (motgate4.mot.com [144.189.100.102]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id DB409C6946; Fri, 22 Feb 2002 15:01:20 -0500 (EST) Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate4.mot.com (motgate4 2.1) with ESMTP id NAA04942; Fri, 22 Feb 2002 13:01:20 -0700 (MST)] Received: [from noah.dma.isg.mot.com (noah.dma.isg.mot.com [150.21.2.29]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id NAA05648; Fri, 22 Feb 2002 13:01:19 -0700 (MST)] Received: from dma.isg.mot.com (ma07-0056.dma.isg.mot.com [150.21.30.201]) by noah.dma.isg.mot.com (8.8.8+Sun/8.8.8) with ESMTP id PAA05179; Fri, 22 Feb 2002 15:01:19 -0500 (EST) Message-ID: <3C76A38E.31328475@dma.isg.mot.com> Date: Fri, 22 Feb 2002 15:01:18 -0500 From: Dan Grossman X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: mallman@grc.nasa.gov Cc: pilc@grc.nasa.gov Subject: Re: new rev of LINK References: <200202200422.XAA27815@lawyers.grc.nasa.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 7bit Mark, Thanks. Here are some comments: The architecture of the Internet was heavily influenced by the end- to-end principle, and in our view it was crucial to the Internet's success. I've always considered this to be a bit of an overstatement, especially in light of draft-iab-arch-changes-00. Suggest toning this down a bit. A third example of link-layer multiplexing is the Data Over Cable Service Interface Specifications. [DOCSIS1] [DOCSIS2] [DOCSIS3] DOCSIS version 1.1 introduces an internal fragmentation and Only one of the references applies here. Suggest: "A third example of data link layer fragmentation is contained in the Data Over Cable Service Interface Specification (DOCSIS) version 1.1 [DOCSIS2]." By the way, text in this section is a bit inaccurate in its use of the term multiplexing to cover the specific case of multiplexing that reduces head-of-line blocking for real time traffic. You might want to try to clean this up. There are several approaches to the problem. The first is to encode each IP packet into one or more SNDUs, with no SNDU containing pieces of more than one IP packet, and padding out the last SNDU of the AAL2 allows packets to be multiplexed into cell streams in ways that the start of a packet does not correspond to the start of a cell. See draft-ietf-pppext-ppp-over-aal2-02.txt as the first in a new IP packet. The AAL5 (ATM Adaption Layer 5) scheme used with ATM is an example of this approach, though it adds other features, including a payload length field and a payload CRC. The payload length field and CRC are an integral part of delineation (needed to detect loss of the last cell in an SDU), as well as being needed to protect against bit errors and erasures. Suggest removing the last clause of the last sentence. In AAL5, the 1-bit per segment flag, carried in the ATM header, The ATM User-User Indication (its proper name) is not a one-bit per cell (again, the proper name) flag, since the field in which it is encoded in fact encodes 8 values in 3 bits. The sentence should read: "In AAL5, the ATM User-User Indication, which is encoded in the Payload Type field of an ATM cell,..." indicates the end of a packet. (This bit is not protected by the ATM checksum, indicating the need for an end-to-end checksum.) The Not true. The HEC covers the entire cell header. Delete the parenthetical statement. packet control information (trailer) is located at the end of the segment. Placing the trailer in a fixed position may simplify hardware reassembly. Last sentence is gratuitous, and facilitating hardware reassembly was at or near the bottom of a list of rationales for placing it where it was placed. Suggest removing this. The ideal subnetwork for IP is connectionless. Connection-oriented networks that dedicate minimal resources to each connection (e.g., ATM) are a distant second, and connection-oriented networks that dedicate a fixed amount of capacity to each connection (e.g., the PSTN, including ISDN) are the least efficient. If such subnetworks must be used to carry IP, their call-processing systems should be capable of rapid call set-up and tear-down. This paragraph has always kinda bothered me as being conclusory. Suggest the following: "Purely connectionless subnets (such as Ethernet), which have no state and dynamically share resources, are optimal to supporting best effort IP, which is stateless and dynamically shares resources. Connection-oriented packet networks (such as ATM and Frame Relay), which have state and dynamically share resources, are less optimal, since best effort IP does not benefit from the overhead of creating and maintaining state. Connection-oriented circuit switched networks (including the PSTN and ISDN) both have state and statically allocate resources for a call, and thus not only require state creation and maintenance overhead, but also do not benefit from the efficiencies of statistical sharing of capacity inherent in IP. In any event, if an SNDCF that opens and closes subnet connections is used support IP, care should be taken to make sure that call processing in the subnet can keep up with relatively short holding times." Or words to that effect. You might even want to move that last bit up a paragraph or two. Bandwidth on Demand (BoD) Subnets Wireless networks, including both satellite and terrestrial, may use Bandwidth on Demand (BoD). Bandwidth on demand, which is implemented systems, is currently one proposed mechanism to efficiently share I know we went throught this once, but the definition of BoD, and what's encompassed and conflicts with other use of this term are really not clear. Are DOCSIS upstream and other contention-reservation systems BoD, for example? How about ATM/Frame Relay SVCs? ISDN? Is there some better way of scoping this thing? Might want to change that to "... is one mechanism that is used to..." (it's no longer a proposal, it's being used for better or worse). Unlike ARQ, FEC was seldom used for telecommunications outside of deep space links until the 1990s. It is now nearly universal in Seems to me that trellis coding came into voiceband modems in the mid-1980s, and that GEOs and military stuff were using it even earlier. Some systems use hybrid combinations of ARQ layered atop FEC; V.90 dialup modems with V.42bis error control are one example. Most errors are corrected by the trellis (FEC) code within the V.90 modem, and most that remain are detected and corrected by the ARQ mechanisms in V.42bis. Two corrections: V.90 has trellis coding only in the upstream (the reasons are too complex for my simple mind to capture). Text can either read: "V.90 modems (in the upstream direction)..." or "V.34 modems..." Also, MNP4 and LAPM are defined in in V.42, not V.42 bis. It is therefore highly desirable that a subnetwork subject to outages not silently discard packets during an outage. Ideally, it should define an interface to the next higher layer (i.e., IP) that allows it to refuse packets during an outage, and to automatically ask IP for new packets when it is again able to deliver them. If it cannot do this, then the subnetwork should hold onto at least some of the packets it accepts during an outage and attempt to deliver them when the subnetwork comes back up. When packets are discarded, IP should be notified so that the appropriate ICMP messages can be sent. Shouldn't TTL get decremented appropriately here (and packets discarded when it reaches 0?) When demand exceeds link capacity long enough to fill the queue, packets must be dropped. The traditional action of dropping the most recent packet ("tail dropping") is no longer recommended [RED93], but it is still widely practiced. The reference should be to RFC 2309 and RFC2914/BCP41 A new technique called "Explicit Congestion Notification" (ECN) allows routers to directly signal congestion to hosts without dropping packets. This is done by setting a bit in the IP header. Since this is currently an optional behavior (and, longer term, there will always be the possibility of congestion in portions of the network which don't support ECN), the lack of an ECN bit MUST NEVER be interpreted as a lack of congestion. Thus, for the foreseeable future, TCP MUST interpret a lost packet as a signal of congestion. Should reference RFC3168 work with TCP Explicit Congestion Notification (ECN) semantics [RFC2481] [RFB01]. Routers at the edges of the subnet, rather than shaping, would set the ECN bit in those IP packets that are received Again, the reference should be RFC3168 (obsoletes 2481) From owner-pilc@grc.nasa.gov Sun Feb 24 06:44:24 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10139 for ; Sun, 24 Feb 2002 06:44:23 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 19D966410A for ; Sun, 24 Feb 2002 06:44:20 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id GAA17684 for pilc-outgoing; Sun, 24 Feb 2002 06:33:23 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id GAA17680 for ; Sun, 24 Feb 2002 06:33:22 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id GAA07712 for ; Sun, 24 Feb 2002 06:33:21 -0500 (EST) Received: from localhost (unknown [211.187.20.219]) by seraph3.grc.nasa.gov (Postfix) with SMTP id 29F71640FB for ; Sun, 24 Feb 2002 06:33:15 -0500 (EST) Reply-To: ljh2877@yohoo.co.kr From: ¾ÆÀÌÇɱ¸¹ÌÁö»ç To: pilc@grc.nasa.gov Subject: ¼­¿ï´ë ¼±»ý´ÔµéÀÇ ¼ö´ÉÄÛ ³»½ÅÄÛ[±¤°í] Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Sun, 24 Feb 2002 20:30:14 +0900 Message-Id: <20020224113315.29F71640FB@seraph3.grc.nasa.gov> Sender: owner-pilc@grc.nasa.gov Precedence: bulk ¼­¿ï´ë ¼±»ý´ÔµéÀÇ ¾ß½ÉÀÛ
¾ÆÀÌÇɹٷΰ¡±â
¾ÆÁ÷µµ ¹Ð¸®´Â Á¾ÀÌÇнÀÁö¸¦ ÇϽʴϱî?
Çпø °¡±âµµ ½ÈÀ¸½ÃÁÒ?
ÀÌÁ¨ Ãë¹Ì»ýȰ ÇϽø鼭 ¼ºÀûÀ» ¿Ã¸®¼¼¿ä.
21¼¼±â »ç±³À°Àº Çпøµµ °ú¿Üµµ ÇнÀÁöµµ ¾Æ´Ñ
¾ÆÀÌÇÉ Çϳª¸é ÃæºÐ ÇÕ´Ï´Ù.
"¼ö´É ÄÛ! ³»½Å ÄÛ! ¾ÆÀÌÇÉ Çѹ濡..."


¼ö½Å°ÅºÎÇÕ´Ï´Ù

»ó¾÷¼º ±¤°í¸ÞÀÏÀ» º¸³»°Ô µÇ¾î¼­ Á¤¸»Á˼ÛÇÕ´Ï´Ù
´ÔÀÇ ¸ÞÀÏÁÖ¼Ò´Â ÀÎÅͳݿ©ÇàÀ» ÇÏ´Ù ¼öÁýÇÏ¿´À¾´Ï´Ù.
ÀúÈñ´Â ±ÍÇÏ¿¡ ´ëÇØ ¾î¶°ÇÑ Á¤º¸µµ °¡Áö°íÀÖÁö¾Ê½À´Ï´Ù
¼ö½Å°ÅºÎ¸¦ ÇØÁÖ½Ã¸é ´ÙÀ½ºÎÅÍ´Â µÎ¹ø´Ù½Ã ¸ÞÀÏÀ» º¸³»Áö ¾Ê°Ú½À´Ï´Ù
From owner-pilc@grc.nasa.gov Sun Feb 24 07:34:22 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10493 for ; Sun, 24 Feb 2002 07:34:21 -0500 (EST) From: owner-pilc@grc.nasa.gov Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id E2383640C9 for ; Sun, 24 Feb 2002 07:34:21 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id HAA22013 for pilc-outgoing; Sun, 24 Feb 2002 07:25:54 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id HAA22009 for ; Sun, 24 Feb 2002 07:25:53 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id HAA13010 for ; Sun, 24 Feb 2002 07:25:53 -0500 (EST) Received: from GLUON (209246018130.customer.ionix.net [209.246.18.130]) by seraph2.grc.nasa.gov (Postfix) with SMTP id 29DF7C68F1 for ; Sun, 24 Feb 2002 07:25:50 -0500 (EST) Subject: We've dropped prices! Come see. MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="====_ABC123456j7890DEF_====" X-Priority: 3 X-MSMail-Priority: Normal X-Unsent: 1 Message-Id: <20020224122550.29DF7C68F1@seraph2.grc.nasa.gov> Date: Sun, 24 Feb 2002 07:25:50 -0500 (EST) To: undisclosed-recipients: ; Sender: owner-pilc@grc.nasa.gov Precedence: bulk --====_ABC123456j7890DEF_==== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit ---------- Virus Warning Message from acs-viruswall.grc.nasa.gov ---------- Found virus PE_NIMDA.E in file sample.exe The file is deleted. A file previously attached to this message contained a virus and was removed. The sender has been notified. ---------- Virus Warning Message from acs-viruswall.grc.nasa.gov ---------- --====_ABC123456j7890DEF_==== Content-Type: multipart/alternative; boundary="====_ABC09876j54321DEF_====" --====_ABC09876j54321DEF_==== Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable --====_ABC09876j54321DEF_====-- --====_ABC123456j7890DEF_==== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit ---------- Virus Warning Message from acs-viruswall.grc.nasa.gov ---------- sample.exe is removed from here because it contains a virus. ---------- Virus Warning Message from acs-viruswall.grc.nasa.gov ---------- --====_ABC123456j7890DEF_==== --====_ABC123456j7890DEF_====-- From owner-pilc@grc.nasa.gov Mon Feb 25 06:36:34 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05754 for ; Mon, 25 Feb 2002 06:36:33 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id B3D1D640E9 for ; Mon, 25 Feb 2002 06:36:26 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id GAA04930 for pilc-outgoing; Mon, 25 Feb 2002 06:28:42 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id GAA04926 for ; Mon, 25 Feb 2002 06:28:41 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id GAA19920 for ; Mon, 25 Feb 2002 06:28:40 -0500 (EST) Received: from mailer.wtmea.com (unknown [62.140.66.211]) by seraph3.grc.nasa.gov (Postfix) with SMTP id 8BBE4640BA for ; Mon, 25 Feb 2002 06:28:39 -0500 (EST) Received: (qmail 6209 invoked from network); 25 Feb 2002 11:37:04 -0000 Received: from dolphin.wtmea.com (HELO ieee.org) (1.0.0.8) by wthome.wtmea.com with SMTP; 25 Feb 2002 11:37:04 -0000 Message-ID: <3C7A2052.FB5BDB7F@ieee.org> Date: Mon, 25 Feb 2002 13:30:26 +0200 From: Khaled Elsayed X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 Subject: CFP IEEE Communications Magazine -- Internet Technology Series Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: undisclosed-recipients: ; Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 7bit Appologies if you receive multiple copies. HTML version of this CFP can be found at http://inetseries.tripod.com/cfp.html ---------------------------------------------------------- Call for Papers IEEE Communications Magazine Internet Technology Series Series Editors Michah Lerner (AT&T) and Khaled Elsayed (Cairo University) The Internet Technology series of the IEEE Communications Magazine is calling for original tutorial papers that discuss the following specific topics: - Traffic Engineering for Large Scale IP-based Networks - Performance Enhancement Services and Proxies: Scalable and Practical Methods for Data and Media Services - Verifiable and Affordable Security: Specifiction and Assurance of Security The IEEE Communications Magazine is read by tens of thousands of Communications Society members. The magazine has also been ranked as the number 1 telecommunications journal according to the ISI citation database for year 2000. The papers will be available on the Internet through Communications Magazine Interactive, the WWW edition of the magazine. Details about IEEE Communications Magazine can be found at http://www.comsoc.org/ci/. Sample publications published within the Internet Technology Series can be found in the January 2001 and July 2001 issues of the IEEE Communicarions Magazine. Tentative Schedule ================== Manuscripts due: May 1, 2002 Notification of acceptance: July 1, 2002 Final copy due: One month before final publication date Prospective Magazine issues:Oct. 2002 How to Submit Manuscripts ========================= Article Style Information ========================= Articles should be tutorial in nature and should be written in a style comprehensible to readers outside the specialty of the article. Articles may be edited for content, and will be copyedited for compliance with the magazine's style guidelines. Page proofs will be sent to the contact author for final review prior to publication. Mathematical equations should not be used unless they are vital to the presentation. Even then, they should be kept to a minimum. If the article has numerous equations, please contact the editor handling the manuscript. References should be included only to guide readers to more information on the topic; the reference list should not include every available source (a limit of ten references is recommended). Use footnotes only where necessary. Articles should not exceed 4500 words. Figures and tables should be limited to a combined total of six. If the article exceeds these recommended limits, please contact the editor handling the manuscript. Submission ========================= Electronic submission of manuscripts as either PDF (preferred) or Postscript is required. Please send your submission to both of the series editors: Khaled Elsayed: khaled@ieee.org Michah Lerner: michah@ieee.org From owner-pilc@grc.nasa.gov Mon Feb 25 08:46:31 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09858 for ; Mon, 25 Feb 2002 08:46:31 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 46C8F640F8 for ; Mon, 25 Feb 2002 08:46:33 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id IAA29155 for pilc-outgoing; Mon, 25 Feb 2002 08:37:52 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id IAA29147; Mon, 25 Feb 2002 08:37:50 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id IAA06417; Mon, 25 Feb 2002 08:37:50 -0500 (EST) Received: from erg.abdn.ac.uk (diesel.erg.abdn.ac.uk [139.133.204.76]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id DB4D0C68F4; Mon, 25 Feb 2002 08:37:46 -0500 (EST) Received: from erg.abdn.ac.uk (gresley.erg.abdn.ac.uk [139.133.207.106]) by erg.abdn.ac.uk (8.12.2/8.12.2) with ESMTP id g1PDbJcG019544; Mon, 25 Feb 2002 13:37:20 GMT Message-ID: <3C7A3E0F.8339114F@erg.abdn.ac.uk> Date: Mon, 25 Feb 2002 13:37:16 +0000 From: Gorry Fairhurst Organization: ERG X-Mailer: Mozilla 4.75 (Macintosh; U; PPC) X-Accept-Language: en MIME-Version: 1.0 To: Dan Grossman Cc: mallman@grc.nasa.gov, pilc@grc.nasa.gov Subject: Re: new rev of LINK References: <200202200422.XAA27815@lawyers.grc.nasa.gov> <3C76A38E.31328475@dma.isg.mot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ERG-MailScanner: Found to be clean Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 7bit Dan, see some in-line comments, but mostly agree with you. Dan Grossman wrote: Gorry ------------- > > Mark, > Thanks. > > Here are some comments: > > The architecture of the Internet was heavily influenced by the end- > to-end principle, and in our view it was crucial to the Internet's > success. > I've always considered this to be a bit of an overstatement, especially > in light of draft-iab-arch-changes-00. Suggest toning this down a bit. > --GF: It says "was", and so seems true still to me... > A third example of link-layer multiplexing is the Data Over Cable > Service Interface Specifications. [DOCSIS1] [DOCSIS2] [DOCSIS3] > DOCSIS version 1.1 introduces an internal fragmentation and > > Only one of the references applies here. Suggest: "A third example of > data link layer fragmentation is contained in the Data Over Cable > Service Interface Specification (DOCSIS) version 1.1 [DOCSIS2]." --GF: Yes, this seems fair. > By the > way, text in this section is a bit inaccurate in its use of the term > multiplexing to cover the specific case of multiplexing that reduces > head-of-line blocking for real time traffic. You might want to try to > clean this up. > > There are several approaches to the problem. The first is to encode > each IP packet into one or more SNDUs, with no SNDU containing pieces > > of more than one IP packet, and padding out the last SNDU of the > > AAL2 allows packets to be multiplexed into cell streams in ways that the > start of a packet does not correspond to the start of a cell. See > draft-ietf-pppext-ppp-over-aal2-02.txt -- > > as the first in a new IP packet. The AAL5 (ATM Adaption Layer 5) > scheme used with ATM is an example of this approach, though it adds > other features, including a payload length field and a payload CRC. > The payload length field and CRC are an integral part of delineation > (needed to detect loss of the last cell in an SDU), as well as being > needed to protect against bit errors and erasures. Suggest removing the > last clause of the last sentence. --GF: I don't think we should remove it. The reason for saying this was -- to alert the reader that these were an IMPORTANT part of the design. -- maybe yoyu should delete "though" which kinds of suggests these -- are peripheral elements! > > In AAL5, the 1-bit per segment flag, carried in the ATM header, > > The ATM User-User Indication (its proper name) is not a one-bit per cell > (again, the proper name) flag, since the field in which it is encoded in > fact encodes 8 values in 3 bits. The sentence should read: "In AAL5, > the ATM User-User Indication, which is encoded in the Payload Type field > of an ATM cell,..." --GF: add "1-bit ATM User-User Indication" and I'd be very happy with this > > indicates the end of a packet. (This bit is not protected by the ATM > checksum, indicating the need for an end-to-end checksum.) The > Not true. The HEC covers the entire cell header. Delete the > parenthetical statement. --GF: Yes, I think this has become garbled, agree delete it. > > packet control information (trailer) is located at the end of the > segment. Placing the trailer in a fixed position may simplify > hardware reassembly. > Last sentence is gratuitous, and facilitating hardware reassembly was at > or near the bottom of a list of rationales for placing it where it was > placed. Suggest removing this. --GF: OK. > > The ideal subnetwork for IP is connectionless. Connection-oriented > networks that dedicate minimal resources to each connection (e.g., > ATM) are a distant second, and connection-oriented networks that > dedicate a fixed amount of capacity to each connection (e.g., the > PSTN, including ISDN) are the least efficient. If such subnetworks > must be used to carry IP, their call-processing systems should be > capable of rapid call set-up and tear-down. > > This paragraph has always kinda bothered me as being conclusory. > Suggest the following: > "Purely connectionless subnets (such as Ethernet), which have no state > and dynamically share resources, are optimal to supporting best effort > IP, which is stateless and dynamically shares resources. > Connection-oriented packet networks (such as ATM and Frame Relay), which > have state and dynamically share resources, are less optimal, since best > effort IP does not benefit from the overhead of creating and maintaining > state. Connection-oriented circuit switched networks (including the > PSTN and ISDN) both have state and statically allocate resources for a > call, and thus not only require state creation and maintenance overhead, > but also do not benefit from the efficiencies of statistical sharing of > capacity inherent in IP. > > In any event, if an SNDCF that opens and closes subnet connections is > used support IP, care should be taken to make sure that call processing > in the subnet can keep up with relatively short holding times." > > Or words to that effect. You might even want to move that last bit up a > paragraph or two. --GF: seems good. > Bandwidth on Demand (BoD) Subnets > > Wireless networks, including both satellite and terrestrial, may use > Bandwidth on Demand (BoD). Bandwidth on demand, which is implemented > systems, is currently one proposed mechanism to efficiently share > I know we went throught this once, but the definition of BoD, and what's > encompassed and conflicts with other use of this term are really not > clear. Are DOCSIS upstream and other contention-reservation systems > BoD, for example? How about ATM/Frame Relay SVCs? ISDN? Is there some > better way of scoping this thing? --GF: I would say DOCSIS uses BoD, it's packet-by-packet or once per --few RTT capacity management... SVCs are once per "connection" assignment --as a rule. That's different > > Might want to change that to "... is one mechanism that is used to..." > (it's no longer a proposal, it's being used for better or worse). > > Unlike ARQ, FEC was seldom used for telecommunications outside of > deep space links until the 1990s. It is now nearly universal in > Seems to me that trellis coding came into voiceband modems in the > mid-1980s, and that GEOs and military stuff were using it even earlier. > --GF: Suggest we drop the preface. and start with "FEC is now nearly" > Some systems use hybrid combinations of ARQ layered atop FEC; V.90 > dialup modems with V.42bis error control are one example. Most errors > > are corrected by the trellis (FEC) code within the V.90 modem, and > most that remain are detected and corrected by the ARQ mechanisms in > V.42bis. > > Two corrections: V.90 has trellis coding only in the upstream (the > reasons are too complex for my simple mind to capture). Text can either > read: "V.90 modems (in the upstream direction)..." or "V.34 > modems..." Also, MNP4 and LAPM are defined in in V.42, not V.42 > bis. > -- > It is therefore highly desirable that a subnetwork subject to outages > > not silently discard packets during an outage. Ideally, it should > define an interface to the next higher layer (i.e., IP) that allows > it to refuse packets during an outage, and to automatically ask IP > for new packets when it is again able to deliver them. If it cannot > do this, then the subnetwork should hold onto at least some of the > packets it accepts during an outage and attempt to deliver them when > the subnetwork comes back up. When packets are discarded, IP should > be notified so that the appropriate ICMP messages can be sent. > > Shouldn't TTL get decremented appropriately here (and packets discarded > when it reaches 0?) --GF: I guess according to some RFC authors....but how much of this is -- is atually done. TTL doesn't map to time anymore - if it ever did! > > When demand exceeds link capacity long enough to fill the queue, > packets must be dropped. The traditional action of dropping the most > recent packet ("tail dropping") is no longer recommended [RED93], but > > it is still widely practiced. > > The reference should be to RFC 2309 and RFC2914/BCP41 -- > > A new technique called "Explicit Congestion Notification" (ECN) > allows routers to directly signal congestion to hosts without > dropping packets. This is done by setting a bit in the IP header. > Since this is currently an optional behavior (and, longer term, there > > will always be the possibility of congestion in portions of the > network which don't support ECN), the lack of an ECN bit MUST NEVER > be interpreted as a lack of congestion. Thus, for the foreseeable > future, TCP MUST interpret a lost packet as a signal of congestion. > > Should reference RFC3168 > -- > work with TCP Explicit Congestion Notification (ECN) semantics > [RFC2481] [RFB01]. Routers at the edges of the subnet, rather than > shaping, would set the ECN bit in those IP packets that are received > > Again, the reference should be RFC3168 (obsoletes 2481) -- From owner-pilc@grc.nasa.gov Mon Feb 25 12:02:16 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18799 for ; Mon, 25 Feb 2002 12:02:15 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id AD1646409C for ; Mon, 25 Feb 2002 12:02:17 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id LAA04332 for pilc-outgoing; Mon, 25 Feb 2002 11:54:27 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id LAA04316; Mon, 25 Feb 2002 11:54:25 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id LAA13551; Mon, 25 Feb 2002 11:54:25 -0500 (EST) Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 68311640C2; Mon, 25 Feb 2002 11:53:12 -0500 (EST) Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate2.mot.com (motgate2 2.1) with ESMTP id JAA04581; Mon, 25 Feb 2002 09:53:08 -0700 (MST)] Received: [from noah.dma.isg.mot.com (noah.dma.isg.mot.com [150.21.2.29]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id JAA19574; Mon, 25 Feb 2002 09:53:08 -0700 (MST)] Received: from dma.isg.mot.com (ma07-0056.dma.isg.mot.com [150.21.30.201]) by noah.dma.isg.mot.com (8.8.8+Sun/8.8.8) with ESMTP id LAA13789; Mon, 25 Feb 2002 11:53:07 -0500 (EST) Message-ID: <3C7A6BF2.81F11FF1@dma.isg.mot.com> Date: Mon, 25 Feb 2002 11:53:07 -0500 From: Dan Grossman X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Gorry Fairhurst Cc: mallman@grc.nasa.gov, pilc@grc.nasa.gov Subject: Re: new rev of LINK References: <200202200422.XAA27815@lawyers.grc.nasa.gov> <3C76A38E.31328475@dma.isg.mot.com> <3C7A3E0F.8339114F@erg.abdn.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 7bit Gorry, I'm mostly ok with this, but: > > > The architecture of the Internet was heavily influenced by the end- > > to-end principle, and in our view it was crucial to the Internet's > > success. > > I've always considered this to be a bit of an overstatement, especially > > in light of draft-iab-arch-changes-00. Suggest toning this down a bit. > > > --GF: It says "was", and so seems true still to me... I hope we're not going to play semantic games with the meaning of "was" and "is". We impeached a President over here for doing that :-). If you read the draft, the message from the IAB is that end-to-end is an ideal, but the reality is not the ideal. I'm sure Mark can come up with words that are politically correct and more accurately reflect the reality of the Internet. > > > as the first in a new IP packet. The AAL5 (ATM Adaption Layer 5) > > scheme used with ATM is an example of this approach, though it adds > > other features, including a payload length field and a payload CRC. > > The payload length field and CRC are an integral part of delineation > > (needed to detect loss of the last cell in an SDU), as well as being > > needed to protect against bit errors and erasures. Suggest removing the > > last clause of the last sentence. > --GF: I don't think we should remove it. The reason for saying this was > -- to alert the reader that these were an IMPORTANT part of the design. > -- maybe yoyu should delete "though" which kinds of suggests these > -- are peripheral elements! It seemed out-of-context as well. I'll leave that to Mark. > > > > > > In AAL5, the 1-bit per segment flag, carried in the ATM header, > > > > The ATM User-User Indication (its proper name) is not a one-bit per cell > > (again, the proper name) flag, since the field in which it is encoded in > > fact encodes 8 values in 3 bits. The sentence should read: "In AAL5, > > the ATM User-User Indication, which is encoded in the Payload Type field > > of an ATM cell,..." > --GF: add "1-bit ATM User-User Indication" and I'd be very happy with this > > Except that it's not encoded as one bit! Two of the eight values of the field indicate "AUU == FALSE" and two indicate "AUU == TRUE". The remaining encodings indicate things that are completely different (like "I'm an end-to-end OAM cell", and "I'm a resource management cell"). Try:.."... which is encoded as a binary value in the Payload Type field of an ATM user data cell,..." > > > > Wireless networks, including both satellite and terrestrial, may use > > Bandwidth on Demand (BoD). Bandwidth on demand, which is implemented > > systems, is currently one proposed mechanism to efficiently share > > I know we went throught this once, but the definition of BoD, and what's > > encompassed and conflicts with other use of this term are really not > > clear. Are DOCSIS upstream and other contention-reservation systems > > BoD, for example? How about ATM/Frame Relay SVCs? ISDN? Is there some > > better way of scoping this thing? > > --GF: I would say DOCSIS uses BoD, it's packet-by-packet or once per > --few RTT capacity management... SVCs are once per "connection" assignment > --as a rule. That's different So the defining characteristic of BOD is that it does resource assignments per burst, and the resource can't be held longer than a burst? > > > > not silently discard packets during an outage. Ideally, it should > > define an interface to the next higher layer (i.e., IP) that allows > > it to refuse packets during an outage, and to automatically ask IP > > for new packets when it is again able to deliver them. If it cannot > > do this, then the subnetwork should hold onto at least some of the > > packets it accepts during an outage and attempt to deliver them when > > the subnetwork comes back up. When packets are discarded, IP should > > be notified so that the appropriate ICMP messages can be sent. > > > > Shouldn't TTL get decremented appropriately here (and packets discarded > > when it reaches 0?) > --GF: I guess according to some RFC authors....but how much of this is > -- is atually done. TTL doesn't map to time anymore - if it ever did! It's got multiple personality disorder for sure... but I believe that RFC1812 is pretty specific about when to use it as a timer. rgds Dan. From owner-pilc@grc.nasa.gov Mon Feb 25 13:21:30 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23005 for ; Mon, 25 Feb 2002 13:21:30 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id A775EC698F for ; Mon, 25 Feb 2002 13:19:46 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id NAA26442 for pilc-outgoing; Mon, 25 Feb 2002 13:12:36 -0500 (EST) Received: from guns.lerc.nasa.gov (guns.lerc.nasa.gov [139.88.87.35]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id NAA26438 for ; Mon, 25 Feb 2002 13:12:35 -0500 (EST) Received: from guns.lerc.nasa.gov (localhost.lerc.nasa.gov [127.0.0.1]) by guns.lerc.nasa.gov with ESMTP (NASA LeRC 8.7.4.1/2.01-local) id NAA62625; Mon, 25 Feb 2002 13:12:30 -0500 (EST) Message-Id: <200202251812.NAA62625@guns.lerc.nasa.gov> To: pilc@grc.nasa.gov From: Mark Allman Reply-To: mallman@grc.nasa.gov Subject: next LINK submission Organization: BBN Technologies/NASA GRC Song-of-the-Day: King of Saturday Night Date: Mon, 25 Feb 2002 13:12:30 -0500 Sender: owner-pilc@grc.nasa.gov Precedence: bulk Folks- In a previous email I noted that I was planning on submitting a new rev of LINK on Friday (3/1). However, as it turns out I will be off on Friday and so I'll need to submit the rev on Thursday. So, if you have input please try to get it to me early enough to get the draft shipped off on Thursday. Thanks, allman -- Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/ From owner-pilc@grc.nasa.gov Mon Feb 25 13:30:50 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23573 for ; Mon, 25 Feb 2002 13:30:50 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id B2C5D64139 for ; Mon, 25 Feb 2002 13:29:34 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id NAA00026 for pilc-outgoing; Mon, 25 Feb 2002 13:22:47 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id NAA29990; Mon, 25 Feb 2002 13:22:45 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id NAA29858; Mon, 25 Feb 2002 13:22:43 -0500 (EST) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 064E0C697D; Mon, 25 Feb 2002 13:21:39 -0500 (EST) Received: from isi.edu (sci.isi.edu [128.9.160.93]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g1PILZ005127; Mon, 25 Feb 2002 10:21:35 -0800 (PST) Message-ID: <3C7A80B1.2010101@isi.edu> Date: Mon, 25 Feb 2002 10:21:37 -0800 From: Joe Touch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.6) Gecko/20011120 X-Accept-Language: en-us MIME-Version: 1.0 To: Dan Grossman Cc: Gorry Fairhurst , mallman@grc.nasa.gov, pilc@grc.nasa.gov Subject: Re: new rev of LINK References: <200202200422.XAA27815@lawyers.grc.nasa.gov> <3C76A38E.31328475@dma.isg.mot.com> <3C7A3E0F.8339114F@erg.abdn.ac.uk> <3C7A6BF2.81F11FF1@dma.isg.mot.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 7bit Dan Grossman wrote: > Gorry, > I'm mostly ok with this, but: ... >>> not silently discard packets during an outage. Ideally, it should >>> define an interface to the next higher layer (i.e., IP) that allows >>> it to refuse packets during an outage, and to automatically ask IP >>> for new packets when it is again able to deliver them. If it cannot >>> do this, then the subnetwork should hold onto at least some of the >>> packets it accepts during an outage and attempt to deliver them when >>> the subnetwork comes back up. When packets are discarded, IP should >>> be notified so that the appropriate ICMP messages can be sent. >>> >>>Shouldn't TTL get decremented appropriately here (and packets discarded >>>when it reaches 0?) >>> >>--GF: I guess according to some RFC authors....but how much of this is >>-- is atually done. TTL doesn't map to time anymore - if it ever did! > > It's got multiple personality disorder for sure... but I believe that RFC1812 > is pretty specific about when to use it as a timer. Unfortunately (from 1812): When a router forwards a packet, it MUST reduce the TTL by at least one. If it holds a packet for more than one second, it MAY decrement the TTL by one for each second. The MAY kills using it as a timer at all :-) Joe From owner-pilc@grc.nasa.gov Mon Feb 25 13:43:15 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24165 for ; Mon, 25 Feb 2002 13:43:14 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 04C9CC691C for ; Mon, 25 Feb 2002 13:43:17 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id NAA05398 for pilc-outgoing; Mon, 25 Feb 2002 13:36:43 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id NAA05370; Mon, 25 Feb 2002 13:36:41 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id NAA03199; Mon, 25 Feb 2002 13:36:38 -0500 (EST) Received: from prue.eim.surrey.ac.uk (prue.eim.surrey.ac.uk [131.227.76.5]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 7ED8B64092; Mon, 25 Feb 2002 13:36:29 -0500 (EST) Received: from phaestos.ee.surrey.ac.uk ([131.227.88.14] ident=eep1lw) by prue.eim.surrey.ac.uk with esmtp (Exim 3.33 #4) id 16fPyw-0001HX-00; Mon, 25 Feb 2002 18:36:14 +0000 Date: Mon, 25 Feb 2002 18:36:11 +0000 (GMT) From: Lloyd Wood X-X-Sender: eep1lw@phaestos.ee.surrey.ac.uk Reply-To: Lloyd Wood To: Joe Touch Cc: Dan Grossman , Gorry Fairhurst , , Subject: Re: new rev of LINK In-Reply-To: <3C7A80B1.2010101@isi.edu> Message-ID: Organization: speaking for none X-url: http://www.ee.surrey.ac.uk/Personal/L.Wood/ X-no-archive: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanner: exiscan *16fPyw-0001HX-00*jxw8mCeI6e.* (SECM, UniS) Sender: owner-pilc@grc.nasa.gov Precedence: bulk On Mon, 25 Feb 2002, Joe Touch wrote: > >>> not silently discard packets during an outage. Ideally, it should > >>> define an interface to the next higher layer (i.e., IP) that allows > >>> it to refuse packets during an outage, and to automatically ask IP > >>> for new packets when it is again able to deliver them. If it cannot > >>> do this, then the subnetwork should hold onto at least some of the > >>> packets it accepts during an outage and attempt to deliver them when > >>> the subnetwork comes back up. When packets are discarded, IP should > >>> be notified so that the appropriate ICMP messages can be sent. > >>> > >>>Shouldn't TTL get decremented appropriately here (and packets discarded > >>>when it reaches 0?) > >>> > >>--GF: I guess according to some RFC authors....but how much of this is > >>-- is atually done. TTL doesn't map to time anymore - if it ever did! > > > > It's got multiple personality disorder for sure... but I believe that RFC1812 > > is pretty specific about when to use it as a timer. > > > Unfortunately (from 1812): > > When a router forwards a packet, it MUST reduce the TTL > by at least one. If it holds a packet for more than one > second, it MAY decrement the TTL by one for each second. > > The MAY kills using it as a timer at all :-) (not following this thread in detail, sorry) note that the definition of hop limit for IPv6 in RFC2460 is explicit. mapping TTL to time in ms is quite simply unworkable in routers. but ttl decrementing (and IPv4 header checksum recalculation) is very much an IP-level function, and something to do on egress from the router, not ingress from a link. L. PGP From owner-pilc@grc.nasa.gov Mon Feb 25 14:10:29 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25406 for ; Mon, 25 Feb 2002 14:10:28 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 0D95DC68F9 for ; Mon, 25 Feb 2002 14:09:11 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id OAA14207 for pilc-outgoing; Mon, 25 Feb 2002 14:01:25 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id OAA14191; Mon, 25 Feb 2002 14:01:24 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id OAA08117; Mon, 25 Feb 2002 14:01:15 -0500 (EST) Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id A74DD640EF; Mon, 25 Feb 2002 13:58:43 -0500 (EST) Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate2.mot.com (motgate2 2.1) with ESMTP id LAA10272; Mon, 25 Feb 2002 11:58:36 -0700 (MST)] Received: [from noah.dma.isg.mot.com (noah.dma.isg.mot.com [150.21.2.29]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id LAA27637; Mon, 25 Feb 2002 11:58:35 -0700 (MST)] Received: from dma.isg.mot.com (ma07-0056.dma.isg.mot.com [150.21.30.201]) by noah.dma.isg.mot.com (8.8.8+Sun/8.8.8) with ESMTP id NAA14845; Mon, 25 Feb 2002 13:58:35 -0500 (EST) Message-ID: <3C7A895A.145ACFAE@dma.isg.mot.com> Date: Mon, 25 Feb 2002 13:58:34 -0500 From: Dan Grossman X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Joe Touch Cc: Gorry Fairhurst , mallman@grc.nasa.gov, pilc@grc.nasa.gov Subject: Re: new rev of LINK References: <200202200422.XAA27815@lawyers.grc.nasa.gov> <3C76A38E.31328475@dma.isg.mot.com> <3C7A3E0F.8339114F@erg.abdn.ac.uk> <3C7A6BF2.81F11FF1@dma.isg.mot.com> <3C7A80B1.2010101@isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 7bit Oooops... I misremembered the "MAY" as a "MUST". Now I'm curious. Does anybody on the list happen to know why it's not a "MUST" or a "SHOULD"? Joe Touch wrote: > Dan Grossman wrote: > > > Gorry, > > I'm mostly ok with this, but: > ... > > >>> not silently discard packets during an outage. Ideally, it should > >>> define an interface to the next higher layer (i.e., IP) that allows > >>> it to refuse packets during an outage, and to automatically ask IP > >>> for new packets when it is again able to deliver them. If it cannot > >>> do this, then the subnetwork should hold onto at least some of the > >>> packets it accepts during an outage and attempt to deliver them when > >>> the subnetwork comes back up. When packets are discarded, IP should > >>> be notified so that the appropriate ICMP messages can be sent. > >>> > >>>Shouldn't TTL get decremented appropriately here (and packets discarded > >>>when it reaches 0?) > >>> > >>--GF: I guess according to some RFC authors....but how much of this is > >>-- is atually done. TTL doesn't map to time anymore - if it ever did! > > > > It's got multiple personality disorder for sure... but I believe that RFC1812 > > is pretty specific about when to use it as a timer. > > Unfortunately (from 1812): > > When a router forwards a packet, it MUST reduce the TTL > by at least one. If it holds a packet for more than one > second, it MAY decrement the TTL by one for each second. > > The MAY kills using it as a timer at all :-) > > Joe From owner-pilc@grc.nasa.gov Mon Feb 25 14:46:17 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26973 for ; Mon, 25 Feb 2002 14:46:16 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 78C46640C7 for ; Mon, 25 Feb 2002 14:46:18 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id OAA26362 for pilc-outgoing; Mon, 25 Feb 2002 14:39:26 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id OAA26352; Mon, 25 Feb 2002 14:39:24 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id OAA15598; Mon, 25 Feb 2002 14:39:22 -0500 (EST) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 36B2E64093; Mon, 25 Feb 2002 14:39:22 -0500 (EST) Received: from isi.edu (sci.isi.edu [128.9.160.93]) by boreas.isi.edu (8.11.6/8.11.2) with ESMTP id g1PJdI006187; Mon, 25 Feb 2002 11:39:18 -0800 (PST) Message-ID: <3C7A92EA.9020604@isi.edu> Date: Mon, 25 Feb 2002 11:39:22 -0800 From: Joe Touch User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.6) Gecko/20011120 X-Accept-Language: en-us MIME-Version: 1.0 To: Dan Grossman Cc: Gorry Fairhurst , mallman@grc.nasa.gov, pilc@grc.nasa.gov Subject: Re: new rev of LINK References: <200202200422.XAA27815@lawyers.grc.nasa.gov> <3C76A38E.31328475@dma.isg.mot.com> <3C7A3E0F.8339114F@erg.abdn.ac.uk> <3C7A6BF2.81F11FF1@dma.isg.mot.com> <3C7A80B1.2010101@isi.edu> <3C7A895A.145ACFAE@dma.isg.mot.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 7bit Dan Grossman wrote: > Oooops... I misremembered the "MAY" as a "MUST". Now I'm curious. Does anybody > on the list happen to know why it's not a "MUST" or a "SHOULD"? It's in RFC1812, later on in the same section on TTL: In this specification, we have reluctantly decided to follow the strong belief among the router vendors that the time limit function should be optional. They argued that implementation of the time limit function is difficult enough that it is currently not generally done. They further pointed to the lack of documented cases where this shortcut has caused TCP to corrupt data (of course, we would expect the problems created to be rare and difficult to reproduce, so the lack of documented cases provides little reassurance that there haven't been a number of undocumented cases). Joe From owner-pilc@grc.nasa.gov Mon Feb 25 17:37:55 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02509 for ; Mon, 25 Feb 2002 17:37:55 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id DFD77C699A for ; Mon, 25 Feb 2002 17:37:39 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id RAA14765 for pilc-outgoing; Mon, 25 Feb 2002 17:28:15 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id RAA14752 for ; Mon, 25 Feb 2002 17:28:14 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id RAA15783 for ; Mon, 25 Feb 2002 17:28:11 -0500 (EST) Received: from almso1.proxy.att.com (almso1.att.com [192.128.167.69]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 9681AC696B for ; Mon, 25 Feb 2002 17:27:21 -0500 (EST) Received: from attrh3i.attrh.att.com ([135.71.62.12]) by almso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id g1PMRJW28171 for ; Mon, 25 Feb 2002 17:27:20 -0500 (EST) Received: from occlust04evs1.ugd.att.com (135.71.164.12) by attrh3i.attrh.att.com (5.5.029) id 3C0695050156924B for pilc@grc.nasa.gov; Mon, 25 Feb 2002 17:26:07 -0500 content-class: urn:content-classes:message Subject: RE: new rev of LINK Date: Mon, 25 Feb 2002 17:27:15 -0500 Message-ID: <28F05913385EAC43AF019413F674A0171EBBDE@OCCLUST04EVS1.ugd.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Thread-Topic: new rev of LINK Thread-Index: AcG+At4f1u4Xtx3OTmeGBBHcdMMd0AART/Ww From: "Lai, Wai S (Waisum), ALASO" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by lombok-fi.lerc.nasa.gov id RAA14753 Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 8bit Dan, As you pointed out, multiplexing has different meaning in DOCSIS than in the first example of PPP. Also, fragmentation helps but is not sufficent. I propose the following to clean up the existing text. A third example is Data-Over-Cable Service Interface Specifications (DOCSIS) with typical upstream bandwidths of 2.56 Mb/s or 5.12 Mb/s. To reduce the impact of 1500-byte MTU in DOCSIS 1.0 [DOCSIS1], a data link layer fragmentation mechanism is specified in DOCSIS 1.1 [DOCSIS2]. To accommodate the installed base, DOCSIS 1.1 must be backward compatible with DOCSIS 1.0 cable modems, which generally do not support fragmentation. Under the co-existence of DOCSIS 1.0 and DOCSIS 1.1, the unfragmented large data packets from DOCSIS 1.0 cable modems may affect the quality of service for voice packets from DOCSIS 1.1 cable modems. In this case, it has been shown in [DOCSIS3] that use of bandwidth allocation algorithms can mitigate the effect. Thanks, Wai Sum. Dan Grossman wrote: > A third example of link-layer multiplexing is the Data Over Cable > Service Interface Specifications. [DOCSIS1] [DOCSIS2] [DOCSIS3] > DOCSIS version 1.1 introduces an internal fragmentation and > > Only one of the references applies here. Suggest: "A third example of > data link layer fragmentation is contained in the Data Over Cable > Service Interface Specification (DOCSIS) version 1.1 [DOCSIS2]." By the > way, text in this section is a bit inaccurate in its use of the term > multiplexing to cover the specific case of multiplexing that reduces > head-of-line blocking for real time traffic. You might want to try to > clean this up. From owner-pilc@grc.nasa.gov Wed Feb 27 07:48:16 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19724 for ; Wed, 27 Feb 2002 07:48:15 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id DA58564137 for ; Wed, 27 Feb 2002 07:35:34 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id HAA12033 for pilc-outgoing; Wed, 27 Feb 2002 07:14:54 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id HAA12029 for ; Wed, 27 Feb 2002 07:14:53 -0500 (EST) Received: from seraph2.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id HAA26694 for ; Wed, 27 Feb 2002 07:14:52 -0500 (EST) Received: from localhost (unknown [211.204.131.96]) by seraph2.grc.nasa.gov (Postfix) with SMTP id 86E08C690E for ; Wed, 27 Feb 2002 07:14:50 -0500 (EST) Reply-To: kisroom@yahoo.co.kr From: ¿¡º¥¿¡¼¿ To: pilc@grc.nasa.gov Subject: [±¤°í]¹Ì±¹5À§ Àü¼¼°è24°³±¹ÁøÃâ.½ÅÈ­ÀÇ ³×Æ®¿öÅ© Çѱ¹ÁøÃâ! Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Fri, 17 Dec 1999 09:08:11 +0900 Message-Id: <20020227121450.86E08C690E@seraph2.grc.nasa.gov> Sender: owner-pilc@grc.nasa.gov Precedence: bulk º»¸ÞÀÏÀº Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø ¹× Á¤º¸º¸È£ µî¿¡ °üÇÑ ¹ý·ü Á¦ 50Á¶¿¡ ÀǰÅÇÑ [±¤°í] ¸ÞÀÏÀÔ´Ï´Ù.
ÀüÀÚ¿ìÆí ÁÖ¼Ò ¿Ü ¾î¶°ÇÑ °³ÀÎ Á¤º¸µµ °¡Áö°í ÀÖÁö ¾ÊÀ¸¹Ç·Î ¾È½ÉÇϽñ⠹ٶø´Ï´Ù.
À̸ÞÀÏ ¼ö½ÅÀ» ¿øÄ¡ ¾ÊÀ¸½Ã¸é ¾Æ·¡ÁÖ¼Ò·Î[¼ö½Å°ÅºÎ] ¸¦ÇÏ¿© ÁֽʽÿÀ. ÀúÈñ´Â±ÍÇÏÀÇ Àǻ縦 Á¸ÁßÇÕ´Ï´Ù.
¼ö½Å°ÅºÎµÈ ¸ÞÀÏÀº Àý´ë·Î ¸ÞÀÏÀ» Àç¹ß¼ÛÇÏÁö ¾Ê°Ú½À´Ï´Ù.



¾È³çÇϼ¼¿ä?
Á¤º¸Àü·«¿¬±¸ ¼ÒÀåÀÎ À±Àº±â ¹Ú»ç´Â
"21¼¼±â´Â ½ÅÀÎÀç°¡ À̲ø¾î°¡´Â »çȸ°¡ µÉ °ÍÀ̰í, â¾÷Àǽôë"¶ó°í µµ Çß½À´Ï´Ù.
Á¡Æ÷°¡ ÇÊ¿ä¾ø´Â ½Ã´ë°¡ µµ·¡ÇÒ °ÍÀÔ´Ï´Ù.

ÇзÂÀ» ³»¼¼¿ì´ø ½Ã´ë´Â ÀÌÁ¦ Áö³µ½À´Ï´Ù.
½Å»ç°í¸¦ ÇÏ´Â ½ÅÁö½ÄÀÎÀÇ ½Ã´ë°¡ ¿Â °ÍÀÔ´Ï´Ù.
Çзº¸´Ù´Â idea°¡, ºÐ¼®·Âº¸´Ù´Â ½Çõ·ÂÀÌ ¿ä±¸µÇ´Â½Ã´ëÀÔ´Ï´Ù.
Çзºҹ®, ³ªÀ̺ҹ®, ¼ºº°ºÒ¹®, Àü°øºÒ¹®.´©±¸³ª ÇÒ ¼ö ÀÖ´Â »ç¾÷ÀÔ´Ï´Ù.

Çö Á÷ÀåÀÎÀ̶ó¸é, ³²´Â ½Ã°£¿¡ ºÎ¾÷À¸·ÎÇÏ½Ã¸é µË´Ï´Ù.
¼Ò¹ÚÇÑ ²Þ¸¶Àúµµ ¾ø´Â ºÐÀ̶ó¸é »ç¾çÇÕ´Ï´Ù.
2³â ÀüÀÇ »ýȰ°ú Áö±ÝÀÇ »ýȰÀ» ºñ±³ÇßÀ» ¶§, ¾ÆÁÖ¸¸Á·ÇϽʴϱî?
±×·³, 2³â ÈÄ´Â ¾î¶»°Ô µÉ±î¿ä?

°°Àº ¹®À» ¿­¸é °°Àº °á°ú¹Û¿¡ ³ª¿ÀÁö ¾Ê½À´Ï´Ù.
ÀÌÁ¦ ´Ù¸¥ ¹®À» ¿­¾îº¼ ¶§°¡ µÇ¾ú½À´Ï´Ù.
½ÅÁö½ÄÀÎÀÌ µÇ°íÀÚ ÇϽô ºÐÀº ÁÖÀú¸¶½Ã°í ¿¬¶ôÁֽʽÿä.
±âȸ´Â ÆòµîÇÕ´Ï´Ù.
ÇÏÁö¸¸ º¸»óÀº Â÷µî µË´Ï´Ù.
³ë·ÂÇϽô ºÐÀÌ ¼º°øÇÕ´Ï´Ù.
2³â ÈÄ¿£ ¾öû³­ °á°ú°¡ ÀÖÀ» °ÍÀÔ´Ï´Ù.

»õ·Î¿î ´ÔÀÇ ¹Ì·¡¸¦ ¿¡¼­ ½ÃÀÛÇϽʽÿä..
NFLI ÀǺñÁ¯Àº ¼¼°èÀÎÀÌ Áõ¸íÇÏ¿´½À´Ï´Ù.
¼¼°è20¿©°³±¹¿¡¼­ ÇѹøÀÇ ½ÇÆÐµµ ¾øÀÌ 85% À籸¸ÅÀ²À̶ó´Â
°æÀÌÀûÀÎ ½ÇÀûÀ¸·Î ¼ºÀåÇϰí ÀÖ½À´Ï´Ù.
580¿©°¡ÁöÀÇ ´Ù¾çÇÑ »óǰ±º°ú 70%ÀÇ ÀÚü»ý»êÀ¸·Î °¡°ÝÀ̳ª
ǰÁú°æÀï·Â¿¡¼­ Ÿȸ»çÀÇ ¿ìÀ§¸¦ °í¼öÇÒ¼öÀִ¿øÀÎÀ̶ó ÇÒ¼öÀÖ½À´Ï´Ù.

(Á¦Ç° : »ýȰ¿ëǰ, ¼¼Àç·ù, °Ç°­½Äǰ, È­Àåǰ, ÁÖ¹æ¿ëǰ, Çã¹úÁ¦Ç°, °³Àοëǰ
´ÙÀÌ¾îÆ®½Äǰ, Ä¿ÇÇ¿Í Â÷·ù,½º³¼·ù, ¹Ì³×¶ö Äɾî, ¹ÙÀÌ¿À¿öÆ® ±âŸ)

±×·±µ¥ ȸ»ç°¡ ¾Æ¹«¸® ÁÁ´Ù°í ´ÔÀÌ ¼º°øÀ» Çϴ°ÍÀº ¾Æ´Ï°ÚÁö¿ä...
4¸íÀÇ ¸ÞÆ®¸¯½º¹æ½ÄÀ¸·Î ±¸¼ºµÇ´Â ·¡±×¿¡¼­ ´ÔÀº ¾î¶² ¶óÀο¡¼­ »ç¾÷À»
ÇÏ´À³Äµµ Áß¿äÇÑ ¹®Á¦ÀÌ´Ï ½ÅÁßÇÏ°Ô °áÁ¤À» ÇØ¾ß°ÚÁö¿ä.
¿ì¸® Ŭ·´Àº °¡»óȸ¿øÀ̶ó´Â Á¦µµ¸¦ ±¸ÃàÇÏ¿© °¡ÀÔȸ¿øÀÇ ¸ðµç ³×Æ®¿÷ȸ»çÀÇ
ºñÁ¯À» È®ÀÎÇÏ°í °¡ÀÔÀ» ÇϰԲû ½ÃµµÇÏ¿© ¾öû³­ È£ÀÀÀ» ºÒ·¯ÀÏÀ¸Å°°í ÀÖ½À´Ï´Ù.

ÇÏ·ç 200¸í ÀÌ»óÀÇ È¸¿øÀÌ »õ·Î¿î »ç¾÷À» ÀúÈñŬ·´¿¡¼­ ½ÃµµÇϰí ÀÖ½À´Ï´Ù.
´ÔÀÌ µ¿ÂüÀǻ簡 ÀÖÀ¸½Ã´Ù¸é ù°ÉÀ½ºÎÅÍ ¾È³»ÇϰڽÀ´Ï´Ù.
´ÔÀº ÃÖ¼ÒÇÑÀÇ ÀÇÁö¸¸ ÀÖÀ¸¸é µË´Ï´Ù.
¸ðµç PLANÀº ÀúÈñ°¡ ÀÌ¹Ì ÁغñÇÏ¿´½À´Ï´Ù.
´ÔÀº ÇÕ·ù¸¸ÇÏ¸é µË´Ï´Ù.

¿Â¶óÀÎ ¹«·áµî·ÏÇÏ½Ã°í ´Ù¿î¶óÀÎ Çü¼ºµÇ´Â°Í Á÷Á¢
´Ù¿î¶óÀÎ Á¶È¸¿¡¼­ È®ÀÎÇϼ¼¿ä...
´ç½Å°ú ´ç½ÅÀÌ È«º¸ÇÏ¿© Çü¼ºµÇ´Â ÆÄÆ®³Ê±îÁö
¸ðµÎ ȨÆäÀÌÁö¸¦ ½Ç½Ã°£À¸·Î Áö¿øÇÕ´Ï´Ù.

http://ebiz7.net/myteam/index.php?id= º»ÀξÆÀ̵ð

º»ÀÎÀÇ ¾ÆÀ̵ð´Â ¾Æ·¡¿¡¼­ °¡»ó¸â¹ö µî·ÏÀÇ ¾ÆÀ̵𸦠¸»ÇÕ´Ï´Ù.

º» Ŭ·´¿¡¼­´Â Àý´ë ´ÔÀÇ Àǻ縦 Á¸ÁßÇÕ´Ï´Ù.
º» Ŭ·´À» ¼º°øÀÇ ¹ßÆÇÀ¸·Î »ïÀ¸½Ã±æ ¹Ù¶ø´Ï´Ù.
¾Æ·¡ÀÇ È¨ÆäÀÌÁö¸¦ Ŭ¸¯ÇÏ¿© °¡ÀÔÇϽÅÈÄ ¿¬¶ôÀ» Áֽʽÿä.

¸ðµç ¼º°ø »ç¾÷¿¡´Â ¾ÆÀÌÅÛ°ú ŸÀ̹ÖÀÌ °¡Àå Áß¿äÇÕ´Ï´Ù.
¾Æ¹«¸® ÈǸ¢ÇÑ »ç¾÷µµ ŸÀ̹ÖÀÌ Áö³­ µÚ¿¡´Â ¼º°øÀÇ ±âȸ ¿ª½Ã »ç¶óÁý´Ï´Ù.
±×¸®°í ¿ÀÇÁ¶óÀÎÀ¸·Î¸¸ ÁøÇàÀ» ÇÒ °æ¿ì,¸¹Àº ºÐµéÀÌ µÎ·Á¿òÀ»´À³§´Ï´Ù.

"³ª´Â ¾Æ´Â »ç¶÷ÀÌ º°·Î ¾ø´Âµ¥."
"´Ù¸¥ »ç¶÷¿¡°Ô ¸»ÇÒ ÀÚ½ÅÀÌ ¾ø´Âµ¥."
"½Ã°£ÀÌ ¾ø¾î¼­ ¸øÇØ¿ä."
" ¿­½ÉÈ÷ ÇØµµ ¼öÀÔÀÌ ¾ÈµÅ¿ä."

³×Æ®¿öÅ© ¸¶ÄÉÆÃÀ» ¿ÀÇÁ¶óÀκ¸´Ù´Â ÀÎÅͳÝÈ«º¸¿¡ ÁßÁ¡ÀûÀ¸·Î ¶Ù´Â ÆÀÀ¸·Î ´©±¸³ª ½±°Ô »ç¾÷À» ÁøÇàÇÏ½Ç ¼ö ÀÖ½À´Ï´Ù.
¿äÁò °æ±â°¡ ¾È ÁÁ¾Æ ¼öÀÔÀÌ ÀûÀº ºÐµé,ºÎ¾÷À» ¿øÇÏ´Â ºÐµé,°¡Á¤ ÁֺΠµîµî ´©±¸³ª ÇÏ½Ç ¼ö ÀÖ½À´Ï´Ù.(ÀçÅñٹ«)

Ý£¸¦ âÃâÇÏ´Â °¡Àå ÁÁÀº ¹æ¹ýÀº »õ·Î¿î ±âȸ¸¦ ¹ß°ßÇÏ°í ¸¸µé¾î³»´Â °Í ÀÔ´Ï´Ù.
ÀÎÅÍ³Ý °æÁ¦¿¡¼­´Â »õ·Î¿î ±âȸ¸¦ ´©°¡ ¾ó¸¶³ª »¡¸® Æ÷ÂøÇÏ´À³Ä°¡ ¼º°øÀÇ °ü°ÇÀÌ µÇ°í ÀÖ½À´Ï´Ù.
ÀÎÅÍ³Ý ¼¼»ó¿¡¼­ 1³âÀº ¿¹ÀüÀÇ 10³â°ú °°½À´Ï´Ù. ´ÔÀÇ ºü¸¥ Çൿ¸¸ÀÌ Á¤º¸ÀÇ °¡Ä¡¸¦ »ì¸± ¼ö ÀÖ½À´Ï´Ù.
±×·¯³ª ½ÃÀå¼±Á¡À» ÇÒ ¼ö ÀÖ´Â »ç¾÷Àû ŸÀ̹ÖÀº ¹é¸¸ÀåÀÚÀÇ °¡´É¼ºÀ» Çö½ÇÈ­ ÇÒ ¼ö ÀÖ´Â ÃÖ°íÀÇ Á¶°ÇÀÎ °Í ÀÔ´Ï´Ù.

Áø½ÉÀ¸·Î ±ÇÇÏ°í ½Í½À´Ï´Ù. ¿ì¸®°¡ Æò»ýÀ» »ì¾Æ°¡¸é¼­ ÀÌó·³ ÁÁÀº »ç¾÷ ±âȸ´Â ½±°Ô¿ÀÁö ¾ÊÀ» °Í ÀÔ´Ï´Ù.
¸¶Áö¸·À¸·Î ÀÌ ±ÛÀÌ ¿©·¯ºÐ¿¡°Ô ºÒÆíÀ» ³¢ÃƵå·È´Ù¸é ´Ù½ÃÇѹø »ç°úµå¸³´Ï´Ù.

Áñ°Å¿î ÇÏ·çµÇ½Ê½Ã¿À.

10³â ¾È¿¡´Â ½±°Ô ¿ÀÁö ¾ÊÀ» ¼¼°èÀûÀÎ e-ºñÁö´Ï½ºÀÇ ±âȸ¸¦ °áÄÚ ³õÄ¡Áö ¸¶½Ê½Ã¿À.
±×·³ ´õÀÚ¼¼ÇÑ ¾Ë°í½ÍÀ¸½Ã¸é ¾Æ·¡ÁÖ¼Ò¸¦ Ŭ¸¯ÇϽʽÿä.

ȨÆäÀÌÁö¹Ù·Î°¡±â

e-mail :kisroom@yahoo.co.kr

¼ÕÆù : 016-9757-2535
From owner-pilc@grc.nasa.gov Wed Feb 27 13:03:24 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06853 for ; Wed, 27 Feb 2002 13:03:22 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 21CA8C6932 for ; Wed, 27 Feb 2002 13:02:59 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id MAA21457 for pilc-outgoing; Wed, 27 Feb 2002 12:55:11 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id MAA21453 for ; Wed, 27 Feb 2002 12:55:09 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id MAA29435 for ; Wed, 27 Feb 2002 12:55:09 -0500 (EST) Received: from localhost (unknown [211.217.173.10]) by seraph3.grc.nasa.gov (Postfix) with SMTP id 28ECA640CC for ; Wed, 27 Feb 2002 12:55:01 -0500 (EST) Reply-To: gotours@dreamwiz.com From: ¿©Çà°¡ÀÚ To: pilc@grc.nasa.gov Subject: [À̺¥Æ®±¤°í]¹«·á ȸ¿ø°¡ÀÔ ÇϽøé ÇØ¿Ü ¹«·á ¿©Çà±ÇÀ» µå¸³´Ï´Ù. Mime-Version: 1.0 Content-Type: text/html; charset="ks_c_5601-1987" Date: Thu, 28 Feb 2002 02:49:48 +0900 Message-Id: <20020227175501.28ECA640CC@seraph3.grc.nasa.gov> Sender: owner-pilc@grc.nasa.gov Precedence: bulk ¿©Çà°¡ÀÚ ¿ÀÇ ±â³äÀ¸·Î ȸ¿ø °¡ÀԽà [ű¹,Çʸ®ÇÉ,»çÀÌÆÇ] ¹«·á ÇØ¿Ü ¿©Çà±ÇÀ» µå¸³´Ï´Ù.


[À̺¥Æ®1] = ¿©Çà°¡ÀÚ È¨ÆäÀÌÁö ¿ÀÇ ±â³äÀ¸·Î ȸ¿ø °¡ÀԽà [ű¹,Çʸ®ÇÉ,»çÀÌÆÇ]
¹«·á ÇØ¿Ü ¿©Çà±ÇÀ» µå¸³´Ï´Ù.   [Ç×°ø±Ç º°µµ ]
±â°£ : 2002³â 2¿ù18ÀÏ ~ 4¿ù 30ÀÏ ±îÁö ´ë»ó : ¿©Çà°¡ÀÚ ½Å±Ôȸ¿ø °¡ÀÔÀÚ Àü¿øÁõÁ¤

[À̺¥Æ®2] = ÁÖÀ§ÀÇ °áÈ¥ÇϽô ºÐµé¿¡°Ô ÀúÈñ ¿©Çà°¡ÀÚ¸¦ ¼Ò°³½ÃÄÑ Áּż­ ½ÅÈ¥¿©ÇàÀÌ 
°è¾àµÇ¸é °è¾à°ú µ¿½Ã¿¡ °èÁ·ΠÀϱݠ50,000¿øÀ» ÀÔ±ÝÇØ µå¸³´Ï´Ù.
(´Ü Á¦ÁÖµµ ½ÅÈ¥¿©ÇàÀº 20,000¿ø) 

 ¿©Çà°¡ÀÚ È¨ÆäÀÌÁö ¹Ù·Î°¡±â
 

±ÍÇÏÀÇ ½Â¶ô¾øÀÌ È«º¸¼º ÀüÀÚ ¿ìÆíÀ» º¸³»°Ô µÈ Á¡ Á¤ÁßÈ÷ »ç°ú µå¸³´Ï´Ù.
Á¤º¸Åë½Å¸ÁÀÌ¿ëÃËÁø¹ý ±ÔÁ¤À» ÁؼöÇÏ¿© ±¤°í¸ÞÀÏÀÓÀ» Ç¥½ÃÇÏ¿´À¸¸ç, ¼ö½Å°ÅºÎ ÀåÄ¡¸¦ ¸¶·ÃÇϰí ÀÖ½À´Ï´Ù.
±ÍÇÏÀÇ ÀüÀÚ ¿ìÆí ÁÖ¼Ò´Â ÀÎÅÍ³Ý »óÀÇ °ø°³µÈ Àå¼Ò¿¡¼­ ½ÀµæÇÏ¿´À¸¸ç, ÀúÈñ´Â ±ÍÇÏÀÇ ÀüÀÚ¿ìÆí ÁÖ¼Ò ¿Ü ¾î¶°ÇÑ °³ÀÎÁ¤º¸µµ °¡Áö°í ÀÖÁö ¾ÊÀ¸¹Ç·Î ¾È½ÉÇϽñ⠹ٶø´Ï´Ù. ¼ö½ÅÀ» ¿øÄ¡ ¾ÊÀ¸½Ã¸é
¸¦ Ŭ¸¯ÇØ Áֽʽÿä.  

 

From owner-pilc@grc.nasa.gov Thu Feb 28 15:04:28 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16573 for ; Thu, 28 Feb 2002 15:04:28 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 5CFD4C6B39 for ; Thu, 28 Feb 2002 15:03:33 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id OAA16747 for pilc-outgoing; Thu, 28 Feb 2002 14:54:37 -0500 (EST) Received: from guns.lerc.nasa.gov (guns.lerc.nasa.gov [139.88.87.35]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id OAA16739; Thu, 28 Feb 2002 14:54:35 -0500 (EST) Received: from guns.lerc.nasa.gov (localhost.lerc.nasa.gov [127.0.0.1]) by guns.lerc.nasa.gov with ESMTP (NASA LeRC 8.7.4.1/2.01-local) id OAA30100; Thu, 28 Feb 2002 14:54:34 -0500 (EST) Message-Id: <200202281954.OAA30100@guns.lerc.nasa.gov> To: pilc@grc.nasa.gov Cc: "Aaron Falk" , karn@qualcomm.com From: Mark Allman Reply-To: mallman@grc.nasa.gov Subject: pilc: rev 09 of link submitted Organization: BBN Technologies/NASA GRC Song-of-the-Day: You Date: Thu, 28 Feb 2002 14:54:34 -0500 Sender: owner-pilc@grc.nasa.gov Precedence: bulk Folks- I just sent off rev -09 of LINK. I think I have everyone's comments rolled into this rev. If not, flame away. I imagine that with tomorrow being the I-D deadline that it is going to take awhile for this to pop out in the I-D archive. So, I dropped a copy of the draft at: http://roland.grc.nasa.gov/~mallman/share/link/ Also, in that directory are diffs against the last version of the document (in addition to the full last rev so you can use your favorite differ if you'd like). Enjoy! allman -- Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/ From owner-pilc@grc.nasa.gov Thu Feb 28 17:41:37 2002 Received: from seraph3.grc.nasa.gov (firewall-user@seraph3.lerc.nasa.gov [128.156.10.12]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24052 for ; Thu, 28 Feb 2002 17:41:37 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 7E66F64102 for ; Thu, 28 Feb 2002 17:39:38 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id RAA02285 for pilc-outgoing; Thu, 28 Feb 2002 17:32:50 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id RAA02272 for ; Thu, 28 Feb 2002 17:32:48 -0500 (EST) From: dailythrower@yahoo.com Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id RAA01704 for ; Thu, 28 Feb 2002 17:32:45 -0500 (EST) Received: from yourwebsite.com (evrtwa1-ar13-4-3-033-042.evrtwa1.vz.dsl.gtei.net [4.3.33.42]) by seraph3.grc.nasa.gov (Postfix) with SMTP id 567D8640E7 for ; Thu, 28 Feb 2002 17:31:08 -0500 (EST) Reply-To: makemoney@big-marketing.com To: pilc@grc.nasa.gov Subject: Make $1250 a day with this confidential report Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 28 Feb 2002 14:10:10 -0800 Message-Id: <20020228223108.567D8640E7@seraph3.grc.nasa.gov> Sender: owner-pilc@grc.nasa.gov Precedence: bulk Hello, Just thought I'd fill you in on an amazing Million Dollar report that uncovers confidential information you are not supposed to know about. It reveals hush, hush info like... *How a banking secret, which bankers don't want published, can help you get $5,000 to $15,000 to use for any purpose within 30 days. *How to use a "Back Door" method to get listed on Yahoo. There is a back door to Yahoo that has been kept hush hush until recently. Best of all it takes only 1 minute to do. *How to use an extremely powerful technique to get your web site listed at the top of the major search engines and directories like Yahoo, AOL, Lycos and more within FIVE Business days. This technique is so new it was just introduced to the internet in November 2001. *Get a list of over 100 major corporations offering legitimate work opportunities for telecommute home workers paying $500 to $1,500 per week. In today's economy corporations like Bank of America, Dell Computer, Motorala and many other such companies finding it less costly to hire people to work from their homes. The list includes contact information for the corporations that need your help. *How to open a checking account if you currently are unable to because you have a bad rating with Chex- systems or Telecheck. *How you can get 1,000,000 hits to your web site in 1 year. Even Microsoft has tried to patent this one but can't. *How to get $3,000 to $50,000 within 1 week regard- less of your credit if you currently have a merchant account. *How you can resell this information with a tested, proven Sales Letter that is EXPLODING wiht sales everywhere. WARNING! Check out this updated, FREE REport before you try any other of the many business plans on the internet. This information may not be available much longer. This may be THE LAST TIME you see this report! Get yours before the deadline by sending a Blank Email to: mailto: makemoney@big-marketing.com It will arrive in just a few minutes. Yours truly, Chase From owner-pilc@grc.nasa.gov Thu Feb 28 17:55:04 2002 Received: from seraph2.grc.nasa.gov (firewall-user@seraph2.lerc.nasa.gov [128.156.10.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24596 for ; Thu, 28 Feb 2002 17:55:04 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 92650C694D for ; Thu, 28 Feb 2002 17:55:07 -0500 (EST) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id RAA05727 for pilc-outgoing; Thu, 28 Feb 2002 17:48:58 -0500 (EST) Received: from acs-viruswall.grc.nasa.gov (acs-viruswall.lerc.nasa.gov [139.88.112.21]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id RAA05718; Thu, 28 Feb 2002 17:48:56 -0500 (EST) Received: from seraph3.grc.nasa.gov (localhost [127.0.0.1]) by acs-viruswall.grc.nasa.gov (NASA LeRC 8.9.1.1/8.11.x) with ESMTP id RAA04524; Thu, 28 Feb 2002 17:48:55 -0500 (EST) Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10]) by seraph3.grc.nasa.gov (Postfix) with ESMTP id 5937A64092; Thu, 28 Feb 2002 17:48:55 -0500 (EST) Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate2.mot.com (motgate2 2.1) with ESMTP id PAA28500; Thu, 28 Feb 2002 15:48:54 -0700 (MST)] Received: [from noah.dma.isg.mot.com (noah.dma.isg.mot.com [150.21.2.29]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id PAA15552; Thu, 28 Feb 2002 15:48:53 -0700 (MST)] Received: from dma.isg.mot.com (ma07-0056.dma.isg.mot.com [150.21.30.201]) by noah.dma.isg.mot.com (8.8.8+Sun/8.8.8) with ESMTP id RAA01476; Thu, 28 Feb 2002 17:48:52 -0500 (EST) Message-ID: <3C7EB3D4.B8170953@dma.isg.mot.com> Date: Thu, 28 Feb 2002 17:48:52 -0500 From: Dan Grossman X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: mallman@grc.nasa.gov Cc: pilc@grc.nasa.gov, Aaron Falk , karn@qualcomm.com Subject: Re: pilc: rev 09 of link submitted References: <200202281954.OAA30100@guns.lerc.nasa.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pilc@grc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 7bit Mark, Thanks, much improved. A couple of things still (not to beat a dead horse): >Payload Type field of an ATM cel, indicates the end of a packet. The ^ cell > packet control information (trailer) is located at the end of the >segment. The trailer (at the end of the packet) contains the packet length field and CRC. >Bandwidth on Demand (BoD) Subnets I'm sorry I couldn't specific in previous comments, having needed Gorry's clarification. Let me now suggest the follow replacement words for the first paragraph: "Some subnets allow a number of stations to efficiently share a channel by dynamically assigning transmission opportunities. Transmission opportunities are requested by a station when it has packets to send. The subnet schedules and grants transmission opportunities sufficient to allow the transmitting station to send one or more packets (or packet fragments). We call such subnets Bandwidth on Demand (BoD) subnets. Examples of BoD subnets include Demand Assignment Multiple Access (DAMA) satellite and terrestrial wireless networks, IEEE 802.11 in point coordination function (PCF) mode, and DOCSIS. A connection oriented network (like the PSTN, ATM or Frame Relay) reserves resources on a much longer timescale, and therefore is not a BoD subnet in our taxonomy. >dialup modems (in the upstream direction) with V.42bis error control ^ V.42 rgds Dan Mark Allman wrote: > > Folks- > > I just sent off rev -09 of LINK. I think I have everyone's comments > rolled into this rev. If not, flame away. > > I imagine that with tomorrow being the I-D deadline that it is going > to take awhile for this to pop out in the I-D archive. So, I > dropped a copy of the draft at: > > http://roland.grc.nasa.gov/~mallman/share/link/ > > Also, in that directory are diffs against the last version of the > document (in addition to the full last rev so you can use your > favorite differ if you'd like). > > Enjoy! > > allman > > -- > Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/