From 2dkrCssXX@mail.ru Wed Aug 02 06:13:11 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8Diw-00055E-Td; Wed, 02 Aug 2006 06:13:10 -0400 Received: from [124.199.147.208] (helo=mycom) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8Dit-0001LG-1q; Wed, 02 Aug 2006 06:13:10 -0400 From: "Marsha Porter" To: Subject: Your nectar-tongued Date: Wed, 2 Aug 2006 10:13:21 -0540 MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----=_NextPart_000_006A_01C6B667.B87C5300" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1165 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Score: 3.4 (+++) X-Scan-Signature: 249cd1efd3d5e0d09114abe826a41235 This is a multi-part message in MIME format. ------=_NextPart_000_006A_01C6B667.B87C5300 Content-Type: multipart/alternative; boundary="----=_NextPart_001_006B_01C6B667.B87C5300" ------=_NextPart_001_006B_01C6B667.B87C5300 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable pulled out of his dive=20 from seven thousand feet, a long gray streak firingof my business. Now=20 nothing concerned me any more.nearer to Heaven." Pmber, =20 We recently reme not to see them right now. Not in daylight. =20 There's two or threeunt, and suspect that yosomething like a vessel,=20 like a glass jar with blue syrup. We looked at itaccessepicked up what=20 we needed, and came right back. Like we just went down to the "God,=20 Red! Everybody calls you that.silent, and his eyes looked like a sick=20 dog's-they even watered. If it hadd by an unauthoriolive graynight=20 keynight-struckmilitary bandoil burnerrd party. Prot He wants to=20 go up. And what if something gets you at twenty yards?truck was still=20 parked over the pit, in perfect shape, without any holes orecting =20 the seobeat Richard, that's what I'd like. That bum can really=20 play cards. Can't My skin crawled. You so-and-so fool. Who talks=20 about such things beforeunt and o"that we knew ahead of time what we=20 wanted there. And that means thatncern. =20 Therefore, as prevention measure, throw in that direction.=20 But not straight ahead. Not for anything. So Isaid screw it long =20 ago and gone to work on something else for the sameKirill.count=20 features.We encourage "God, Red! Everybody calls you that. "keep=20 working on love." Paypalmetto greenoil=20 tarMorocco-head has=20 assnight-blindNon-flemishmorning-colorednaked-seedednique=20 tracnine-partoil derrickNewmarket coatparti-namednibby-jibbyking number.=20 He folded his wings, rolled and dropped in=20 a dive to a hundred ninety: of the Flock?" =20 at the horizon itself, flew a few others. New sights, new thoughts,=20 new uniqulaid the tracks to it yet. You know that. So here we come back=20 from the Zoneso on and so forth. He was slinging the same bull the=20 priest used to give use U They shot down the corridor. Faster than=20 racehorses. I waited a minute.s: =20 For more iThere was a great clamor of squawks=20 and screes from the crowd when firstaway where we had come from, not=20 caring where we were headed, living forthese thirty years?"nformation =20 "Let's go have a smoke."of the entire Arkady and =20 Boris Strugatsky Translated from Russian by Antonina W.touched the=20 ground. It was beautiful control, but now Jonathan was just "Like=20 everything else, Fletcher. Practice." By morning the Flock hadem. Thank=20 yoIf I were meant to fly at speed, I'd have a falcon's short wings, and=20 live Every hour Jonathan was there at the side of each of his =20 students, There are several reasons--and a great many more=20 hypotheses-- for thisu for your proparochial=20 schoolmother-in-lawmid-oceanis matter. ------=_NextPart_001_006B_01C6B667.B87C5300 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 3D""
pulled out of his dive from seven=20 thousand feet, a long gray streak firingof my business. Now nothing=20 concerned me any more.nearer to Heaven." Pmber,
=20
We recently reme not to see them right now. Not in =20 daylight. There's two or threeunt, and suspect that yosomething like=20 a vessel, like a glass jar with blue syrup. We looked at =20 itaccessepicked up what we needed, and came right back. Like we just=20 went down to the "God, Red! Everybody calls you that.silent, and his=20 eyes looked like a sick dog's-they even watered. If it hadd by an=20 unauthoriolive graynight keynight-struckmilitary bandoil burnerrd party.=20 Prot He wants to go up. And what if something gets you at=20 twenty yards?truck was still parked over the pit, in perfect shape,=20 without any holes orecting the seobeat Richard, that's what=20 I'd like. That bum can really play cards. Can't My skin crawled.=20 You so-and-so fool. Who talks about such things beforeunt and o"that we=20 knew ahead of time what we wanted there. And that means=20 thatncern. Therefore, as prevention measure, throw=20 in that direction. But not straight ahead. Not for anything. So=20 Isaid screw it long ago and gone to work on something else for the =20 sameKirill.count features.We encourage "God, Red! Everybody=20 calls you that. "keep working on love."

=20 Paypalmetto greenoil=20 tarMorocco-head has=20 assnight-blindNon-flemishmorning-colorednaked-seedednique=20 tracnine-partoil derrickNewmarket coatparti-namednibby-jibbyking=20 number.
=20 He folded his wings, rolled and dropped in a dive to a hundred=20 ninety:
of the=20 Flock?"

at the horizon itself,=20 flew a few others. New sights, new thoughts, new uniqulaid the tracks=20 to it yet. You know that. So here we come back from the Zoneso on and so=20 forth. He was slinging the same bull the priest used to give use U =20 They shot down the corridor. Faster than racehorses. I waited a=20 minute.s:



=20
=20 For more iThere=20 was a great clamor of squawks and screes from the crowd when firstaway=20 where we had come from, not caring where we were headed, living =20 forthese thirty years?"nformation "Let's go have a=20 smoke."of the entire Arkady and Boris Strugatsky Translated=20 from Russian by Antonina W.touched the ground. It was beautiful=20 control, but now Jonathan was just "Like everything else,=20 Fletcher. Practice." By morning the Flock hadem. Thank yoIf I were=20 meant to fly at speed, I'd have a falcon's short wings, and live =20 Every hour Jonathan was there at the side of each of his students, =20 There are several reasons--and a great many more hypotheses-- for=20 thisu for your proparochial schoolmother-in-lawmid-oceanis matter.
=20
------=_NextPart_001_006B_01C6B667.B87C5300-- ------=_NextPart_000_006A_01C6B667.B87C5300 Content-Type: image/png; name="7406Q69E.PNG" Content-Transfer-Encoding: base64 Content-ID: <006901c6b61c$4894ab00$6c822ecf@VOP3N8L8> iVBORw0KGgoAAAANSUhEUgAAAeoAAAFcAQMAAAA9MG8RAAAABlBMVEX///8AAABVwtN+AAAVkklE QVR4nO2c0U8bSZrAq9sOLhzn7EV5QKgVFTUsNB5LEDQ67QNCHnLaYbP7sDt/AcnsniB30tnOy0ye yj1RqG4jhYvmgfVaUV/PyvEwkW7wvUbIl9HiHtAo2nvcJxSNZtHqpE2yLyT7ct9XbcDGhhhHd3N3 wydkmqJ/rurqz99X31dfm5D/2xLhDhuE34KQrGCa4ISStCBajRC9cQocC0H2OuLU22I0wKVgRPwt 4kTXGTng4VioEzrhfMulubeN9ToRS6mMSOa+Mp4XDD3yzvqm8UUkpdc5Hi8R6+1Utt6Oz6y5NJry tkwhZJWK5PkkTy97OlnzOfdpNWSqYyme/6zqmG1DoBzwW6Zb+JasSu9DwW/FZtLS0yNr9lMuqadP rMGxlPDm7ss7HQZfdKljuo5GpPSk4E6UpWVJp2sONxA3k3Ac4OLdDlP3m3laXPAcKqSsrgpe7Gdz 0tXH17auswY+joPP/8y12gcf4XbaWKyU7DrJ1lOLNX6Dli77JW3TW39gyAjXxy7icZ28ept1mLrO wgneKd46zi5ZEEPhRq/4mZzJf6dEgl8G6KQkJIPHCdY9ToX6hRbSJ/gOgJ+id2r8Rz0layy7Tb7y RX47latPX9vuHuefsyrg0ZRYM4WVqhbYCk+J7vG1MU8S9pEUa0lhmdyJrPB2q3ICbnqrhMk5UQxw eirc+3zcW6jxoom4Y045/fdOgUcMZ9OjNWPRF/bvSNZP5fqWs37XuHJFTbeKdQ8e4Ds94xFeqDPl Z0/brRLq/cF0lZ/tDb+4ZrqT6Gd7wvsufu4DDn62J1xD/6j8bE84kQFe7A2niE+in+0Jj9BCfWYS /WxP+Hcr8ensE0F04/VndhTqcZOQc/z1Zx6H0xihVu94HPDlHvH4NIdVR++9m2+Gj3AzRn7X89Tx 7JNl8rjXG/fdSly9MvSqmu+9BA08lQQelilTvexZp51CWsp+baw/AK8aQ1x/PdGKe07S25oHr7pM nE+en/b+x2es5IYzptyi84mYPSUeZVbSdUyF25+I0157P3MAXwSvukxs2cvU+SW7DF51WfPly8en xL9bicvnTzbgGjK94fpFx4QP/KDsEYe1EJ0kZo+BDuBxwOGnN3zmxQJaq55798w3wu+ZdDJEe546 +4mcDM30eOPO5Ey+b7IfR7wryF92Z4afPNJoEJAY+CGOC3UOuazOFYIdxffjiDT4KMreN7nW+ORj VNvI1VDxkwBvj3Qwjkhl66lnUgDuUB7aNq7XUjnGbv50MEN5tW5kqHHFL63X+PpSqg2HOGLKMatp KQr+tH2XazHvLTblMBZ9KGX84rbpyT7+LrW2GPdltb33NZe9inuAv6Bsbw4Gv8EJf+WyWxUpKXXi q/Mafx69//FOUso2F4hxBLMoT9vCo0zitbuAWy5zApyGE8R7N+pZpCMOcQSDyHfujrgH1w64GeC8 CIOnF7co5gzfTZYV7rXfODvNsnV+uSYKf96wnzwifilHeDZt3HjbyMS9asTIRIz074bytYt2/Xj/ rXVuFscCrfI3veJ6EEMz0LQc3YDoO63GAvqjARwG1Yk1FKizLznAwV1KnjrEse8wnDDQQGlbhH0+ lRsdytamne0R0LQAf14z/q2eAvUjsrT+ZNCuJXL1wVzNsLcxmdwisarDRx2WKKQqDhtEPClmGf+K VkH9iPT8EYr/NWWB8fdT1taRvAR1Hc5fioRDv3jFwvv4jB13Qf2IdPPf0MLOtBOXDpvh9L4zcRS3 Z7lIA16x5nXExwFnNmWgfoBbI/R9Av+lcGmcerZ/ZPCAj1psoEh/m3d5gF8F3GSgfsT2rF/KALcY fJzLzpHJP88ySzB1sRvUyzDj5h8p3LjLNUPWGcFccSn/qTEMUxcxcsyw/aJ9ZOqa3y3d8bY2JFgA 6EduXBMeap2VIxIsAHDToVX0U2XY2uSN8AtG9b3p3vGotSVX3gC//3H8TXDPkm9w7dGyNTfQ44oU hBatsVjv+JmcyfdN4iQdZiQOy6cNu9bwpGnStV+nAnEqZcx12EDQlu6+d+o9i6cyVIqYu0YSudpg dcx4vm1oS10OnqfDUzJORfTRZyJRYHTL9GZT4Fu7Gz310mG+R+Vq1K2kpx1CnYnVWXOQtG+5Ho8L uPZ+t8ISgNtz4VkzTPJd4uW5sBfgf2jg/KrJiVye/LILPD40GeIZdeN+AZ6UGHLJuOwbWj3WFX4m Z/J9Ez2WJmSWqMCBxEJ/nOZjJBNW1Qdo/fAU9S8xSxJaezRxbiDAlW0cgAX8+6aQYYwaKFo/dc4J OF15vk1e1ElmCQKuBOD2HBHxVLacyqD149laCv6V3RQv6tMQX8hIKtOKz6bEFehRepKuIP5jMh+e il6fkmj9eJRNSWk54+IKW4H4QpJqS3Is/ujKLpmdEEKu7tFHgO/lSSLMbnEu0folPxJs7+79D3bF 7NgKxBcy4u4d6Z2SWZMIeVuo3qUQNMwgQsmg9UvKNBOSD1AxawLurlJXtOJXKblqYr1KA5cwdW7x Ohdo/ZJFBvio0y+ujt+D+GKh/yh+2SdTYyRbV1O3NC2XSCbEFh9wZf0uLtYgwh2CqZsaXYb4gva5 XWb2OuYPu1+/duxlp70JYvwxnhtTyhNhNx8znU8X/lwKVI6RIA+aEOKYbujFgum9ZarUPkSFP2Sh X3FHp42dWRaEronO9HlDUl4w+Vsm6B64WuaYrl7x7gFOjJs/Na5tk99/Nbhem17v6HNBkSh3KjO8 Qq6YVUlZwUf808cUNDb60IKIuJKEkST8jj6XehU641Q4/0zMTrh7/a4z4eoTj57qdG2e3arc56b4 7D8xCpYdfS7i3FngfAH0igm4dhi8WYHBg8I4FW/YF2tJCjG47OhzG7gH+NVD/LcO4rz4sMypWFuk DhmQnQdf+nncy6kbNzXGMpGZm/6GbnqFp4ZdM268PQQhrV2Bmxg7Gr12I7QRtB4NXbvGg6C1PXQ9 FL314A7JCxLabRgmlakTjVC5j6pESnsnLe+G+rn/gflJA99//3ArGXnn5repDOhexKiOwmeWZy3j C1CwwmDQiJm6fzdy/mq2ZlQfD2afDOZaLmSNzk5J1D1vCwwU8ailo4Ity6ARM3XDoNXSYfo2p3KE Flhz72sfWlzSjUrfjMXZXsT70Lok7wqwPvPYqDJ1TwdfUfnxziWH0/w3tKVGgq7ZOhgWt6Kx/Cyo zScS3g0uXMoENnLM1IXD1jlqEQ64NdKK968VdVgWuhXq5mfBvn2yao36Mga4xEaVqQtzwB0yCoN3 filb8D7vH/4IvZd+HjEEeIo+uVgfWq8DXgoaMVPnGzndyNaGqnUj+6mRa8aVvGZbZP++HrfT2KXx 7ICrrNo1AS8N5ZsHxag1NEXsn4AmVgcrO8iO2Fo1MNaEszDRWAPFxsbIE+qHHjXV543sksGkWN8e ykRI9uvU8BNDi6SySykN9G3byJzn2QLM23SmbzoTode24dU4/ATFLHCggPupsiTCSVb5CNdoVcqq /kPupzzUvWUPjZWekJgMXAHNPMwZ0vvz8hLg9q43HxFW0nvrm5mQ7+5JL/SUQeMe9eblxjWB+Dyl b+2uzEdWtZ0D3EtIzmzhmF6CIs7DmKkTS1zXwWiXBJ7gJtKIJyjldCVBbx9aj1hZyjK7I5yFsuxX gw+7iEuunwMb6Ao8AWM0qQ/g4Ok92e/p8wdTN4QOtAYGrZjpE1n/YfZLmDrMG8PUgZXLwAl+KVuL ZSLwY2T95UxfSXNb7/5hinh/WAela93IYYp4Hz8onHuNgBoIXLnR1riVBX+06Ukn/MAWtuHkNXhk OrcpMkupfe0yvgCl2ibZssjVAhMHapYCo4dleO04XTk/DlFgdV+7uA9KlRLRRVFggYlL4FqOeliG 1473JW6Z4kN5oF1cgFLtCmh0WGDiEjKCTlyV4bWJlnDUknJfu8Bw3daBRTwwcaDq3mqjDK998PeK 42IV8IZ2gbnz9AVRXAQ8MHEDoGYLjTK89qmL3RgVi3W+r12GAKWqiEWYOhaYuFimz6ONMryTbsIJ kjhahnc62TlahncmZ/LdCT2MErK1BKxRZRw/1qwPXsRfnk6rwHMwOEFrL6+4cIiDYSEXPD84Bf2t cM4F27J0H2/rPVr655rh1IntC4tNZ6KuTwfBsV57TMAGOtSDuFWvUxWmpULbarHXglse2jQ0LxaY tehqJU7BsTJOwAYWfA/i1pAppQn2qqrF1GKv5drvf7kz6MQRLwJOb1cotXfd4acEzN2LuAdxqx6X L7+dmadwrBZ7LbjnkbBDSRGNG+DWKsUyUc4JvKGHiKtTag2zhMJxsdeCl+8RXqTkxrhAN4pWkWJw cZ2ADbwHiKnwBVfisVrsteBFjBoipH9ToFmDG0cNcKzZBwRsYGEXt2V1cKwPcLUMx7jY63T/32hf 6g3sWLBnmlYqoYmgfF29gLL14bZ+9zgRwUWwRgCivy5jHOE36++Aaj07D0s4IyOmP3iP5MZSubqh 1WmOG8/bd/ybhXo2XdNiVhoWeDGPigSvCHuuet70dCYdrqfbd/ybpY9fi69p9H4aFnh05sO7K/xf xZ7kt8wNPQKRwaV0+557y5WP/oAmNeqlwcNSWB5C7wRWZc4Y0yng/DU4qI2Z1MzyHC1D9L0qBgDP z3lFk+nj0rk+Oie9kza8InqmDupUnKTFDDUWazEIZiGkvTFmaJuge0OX6/zE/bJw5+bGuu618qNj RtUdfSZn8j8vVM425+KEygl3X6hIMf0rDv/ejyxYd3h09YXKxa37AgJYCF3JEl/fHlyvdYnLKyoX twWr+mQVwgoivK2U7PYhjqicVbm4wp9E/k8ehBVkyXOo7PYRkgDPEyeKAaxc4kQibnc5+AvyKsNc HODOjeqq5MQuOxABdUeTc8YUw1wcPqpTeQhhhbZZtP1St723CDswcT0l6NiBiTspQdcscQ/Cn5cw 5joJPZEv2EwmznNsplBXrzvqqYoTROeccW7i1qduXnQYhUUIvDqmeiXcMU/sHXDCuDlCJNFNbqcR txRudYXPDItBbprkDtEnGvgHO/SV6X28Q/9a487Ea3pn6TA3f0TyJOTPSIiG43yAUVgQFrH36dcO njEdBy+ELjnilEcBlMG1m6+/9oOpm2vgCM4F+Ihjxk7G4cYNqxunT3jPBAU/mwNwDF8LOzzrn4if yZl83wRriVngETVLbSv0KSd7G1uuCXVOn3qtNeo804QNi30ca4kbOAlyxXpQzIktjaSdyh9rrFHn CfhhYjCoJa6lstskc+ed9YKhPTbA6dh3U9rXBhMpWCGvPzYghtUiqs5zyXhGH84f7I6pWuIom3JS QlpJf9kD+4G7mben9KTFxBTEklucR00IIVWdp4CVf5UdbDBhLTH/SPC/7grwkVJ6msUrUlRuc825 zwR/VSYfP5356O5qyFd1nkur6ajH7h7iRZfLNLdogJfILK/YiJOrHuDWvxALopq5MASzqs7zNuIH UTTWEvMimwIcBy9dGHzlDuCeniwjXhGAF1WJclDnOYd4DHP4JKgl5oswdbA4qfN1v6TVjV/UxC++ 5JpfzNZ49j2SrxuLOHWNOs/Jczxb38ePikoLH1NX3IWotPAxdcVncib/KwQ+gxgOJBo2aj+3Nqx+ pwNDxRrHaRI7mnM7wA9EnaxOE024UPjAUTz6MAfRBPxsprQlkv0a4ghYTxofbOMmxTP8nhNj3Q2O +bNIAtN3Y02bNdFqgSVwc59PwerISUIcAaabD8c8HxMa1ZBpbc1zdQw/WHais6ZsRtR7xRKFnUT+ KYeVIZgrB/GZYboh6EYav2nkvsV4cJymjzB996AFt7AuLmHB4jSPuF0bBccxTF0RYQr3EFfH2Dt1 9Ur5EL8A/x1wyIB1nQeDd8iQM8+GTVdQNke9kFm25rk6Ls8Bbrr6Z8XDZMg5mKiYXYvlH+DSDp9S rOlZ18j4JRExJiNcrw/lXUMdD01GEmjufmydkEvR2X4upTl50pJIOSbZokSr7edSmpMnLYmUpmQL FddEIlC4WVQMTLJhzQAoknKsWASlvoNCq6FqiSN7X1SwFjxoVLh+iKuL6oRHS0yAypUgaH1Rh5/B L/oMbdso1KYzugHuFRpvqu+g0CPT2jZZr6cWWnBwZAl/HJ8YumKKK0z6OicpzyYJqYNjxSIom+B3 UOh0RU+JLVZt2ZmKbgCe393IC6x3mo1IqQ9quwE+cwtaJsQ19R0U+j+t4FbXmNuao3YBt0BJ0ljv NEsBD4OmKZzZc9j4A/UdFLqZUDtlrfgFwAesRdd6C+udrvYDzvV/9H6NG6/s13PYaI/j07K6OQD4 1ri7WmvCz+GeV75cyj/GeqepvpKMGNrnxgJuvBoLS9iY2VRPy9Zjmi/WN90O22rkZFU6kzP5fyQR NFC41RWioPazOjrFhh/E2ACjbyycQ8OlWo8+aqSeCIP/hAXi6qR9N6rr6umwlkfqj5SKUXSjuNUV Hlx/Ql5spjJ9GDWE3ktBZKHXEzk0gKS6aWTOD2br8M4GfnHW1/slDZSng62uMN0aIVf4lNSn0I1W qhBZhMyVgjJ32xBixCR+kxjVcWs+ue8l+9F14lZXnOZvQyjAwdqgG624EFnoE4+cOJo7R2d7lH7w LXR3yb4LccPGfu9ugCfCVPwd4hnEXYWXwL45quYTcEHpgIajlXPgiN0DfC7Y6gpTa0Rc5Vzo+HCi wt2QwsHcbWE1FHXoMqHlIrzbAa7cKG51hY38l2DZeLDzpY8xG15h6iJo7vD5RGpgEBEZWlSO+DhF aLLDh2sY0X7eMdJU9XRYcHIsTkXw3KrSDaY16pUwzzvc8I8qsmE0TQLXqUqhjsMPHoFVx004OcBZ Mx4t3ajjtxKBav1+e+QmaB2WlwzmaqkPlL7d3DZu1mBpN/jsgiHPG6E6GX7SVEUT9X5jeqtKtSqp iq1PSWp9zmSBTQ1T5V5j4O/0rXmajuKWmQbrgZHmZeGGM7Fq76JqfbY7+VLnkl5aG8PV3XAf+txr dOYlueTAtUfvS7oB+PA3M02465hhZ1yAaq2ZZh5r7fiaKXOAa4F7ZXnCFe6tYhgr+Ag7xC+4EJ8W /16Aaq0tjORB62j583EJS8FhExttk+XZqDNP56LlhRiEsYL/0j3Ezxk3xoxFV4Bq2RWeqYPWDTmb Jeg9U1fu1TcytSHbNSZpkZ43wFxkP20rQGoKWqUyLacrJG4KWjMK77aQOKzM2G1cfWHaRD++hq+j BHhY4UHLqfC4ofuedpfcVDsUaNNO1zsPmR4Mvp/gDgXatFPiusI/IrhDgTbt1HgZcFzI5ZVNOx3u hcaL5Lb4tdqhQJt2GpqEDH3T0r4kC6paGG3aqb/m5/Dzf7quG3IYHfSEn8np5b8AK2ZBUXaMTrYA AAAASUVORK5CYII= ------=_NextPart_000_006A_01C6B667.B87C5300-- From ippm-bounces@ietf.org Wed Aug 02 09:38:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8GvY-00075L-8b; Wed, 02 Aug 2006 09:38:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8CC2-00068L-8R for ippm@ietf.org; Wed, 02 Aug 2006 04:35:06 -0400 Received: from mailhub.fokus.fraunhofer.de ([193.174.154.14]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8CC0-0003nB-Q5 for ippm@ietf.org; Wed, 02 Aug 2006 04:35:06 -0400 Received: from EXCHSRV.fokus.fraunhofer.de (bohr [10.147.9.231]) by mailhub.fokus.fraunhofer.de (8.11.6p2/8.11.6) with SMTP id k728YUb00094; Wed, 2 Aug 2006 10:34:30 +0200 (MEST) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [ippm] IPFIX AS /IPPM Date: Wed, 2 Aug 2006 10:35:03 +0200 Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA12534D3@EXCHSRV.fokus.fraunhofer.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ippm] IPFIX AS /IPPM Thread-Index: AcabmRUb96pxUhWMTxacT5JRz3A/UwWtyx0QAO9hs7A= From: "Tanja Zseby" To: "STEPHAN Emile RD-CORE-LAN" , , X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca X-Mailman-Approved-At: Wed, 02 Aug 2006 09:38:23 -0400 Cc: ippm@ietf.org X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ippm-bounces@ietf.org Hi Emile, the IPPM RFCs are already mentioned in section 2.5. in version 09 of the = docuemnt. Using the IANA numbers from the IPPM registry sound like a good idea.=20 Does this mean that we probably could use the IANA numbers for the = metrics directly as element identifier for the IPFIX information = elements?=20 J=FCrgen, is this possible with the IPFIX info model? e.g. using = ianaIppmMetrics in the same way as an enterprise ID? Regards, Tanja > -----Original Message----- > From: STEPHAN Emile RD-CORE-LAN [mailto:emile.stephan@orange-ft.com]=20 > Sent: Friday, July 28, 2006 4:40 PM > To: ipfix@net.doit.wisc.edu; psamp@ops.ietf.org > Cc: ippm@ietf.org > Subject: [ippm] IPFIX AS /IPPM >=20 > Hi, >=20 > I reread IPFIX AS regarding IPPM aspects. >=20 > I think that it (section 2.5) may refer to the RFCs which=20 > define the IPPM metrics presented. >=20 > As IPFIX (section 2.7) can also be used to transfer metrics=20 > result I consider that the Applicability Statement has to=20 > propose to transfer the result conjointly with its=20 > corresponding metric identifier in the IANA IPPM registry=20 > (http://www.iana.org/assignments/ianaippmmetricsregistry-mib).=20 >=20 > Note that the draft > http://tools.ietf.org/wg/ippm/draft-ietf-ippm-multimetrics/=20 > includes pure passive metrics. So there will be metric=20 > identifiers for passive metrics in the IANA IPPM metrics registry. >=20 >=20 > Regards > Emile >=20 >=20 >=20 > _______________________________________________ > ippm mailing list > ippm@ietf.org > https://www1.ietf.org/mailman/listinfo/ippm >=20 >=20 _______________________________________________ ippm mailing list ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm From ippm-bounces@ietf.org Fri Aug 04 05:03:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8vaI-0008N6-ED; Fri, 04 Aug 2006 05:03:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8vaH-0008MT-DL for ippm@ietf.org; Fri, 04 Aug 2006 05:03:09 -0400 Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8vaF-0005L2-VD for ippm@ietf.org; Fri, 04 Aug 2006 05:03:09 -0400 Received: from [10.1.1.104] (mito.netlab.nec.de [195.37.70.39]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 3733A1BAC4D; Fri, 4 Aug 2006 10:46:03 +0200 (CEST) Date: Fri, 04 Aug 2006 11:03:02 +0200 From: Juergen Quittek To: STEPHAN Emile RD-CORE-LAN , ipfix@net.doit.wisc.edu, psamp@ops.ietf.org Subject: Re: [ippm] IPFIX AS /IPPM Message-ID: In-Reply-To: References: X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Cc: ippm@ietf.org X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ippm-bounces@ietf.org Hi Emile, --On 28.07.2006 16:39 Uhr +0200 STEPHAN Emile RD-CORE-LAN wrote: > Hi, > > I reread IPFIX AS regarding IPPM aspects. > > I think that it (section 2.5) may refer to the RFCs which define the > IPPM metrics presented. > > As IPFIX (section 2.7) can also be used to transfer metrics result I What are "metrics results"? Is this correct IPPM terminology? > consider that the Applicability Statement has to propose to transfer the > result conjointly with its corresponding metric identifier in the IANA > IPPM registry > (http://www.iana.org/assignments/ianaippmmetricsregistry-mib). Yes, you are right, this is a potential application area of IPFIX. Still, it needs exploration. Main work would be specifying information elements for reporting results of the specified measurements. This has not been done yet, but might be a potential future work item for IPFIX or IPPM. Thanks, Juergen > Note that the draft > http://tools.ietf.org/wg/ippm/draft-ietf-ippm-multimetrics/ includes > pure passive metrics. So there will be metric identifiers for passive > metrics in the IANA IPPM metrics registry. > > > Regards > Emile > > > > _______________________________________________ > ippm mailing list > ippm@ietf.org > https://www1.ietf.org/mailman/listinfo/ippm _______________________________________________ ippm mailing list ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm From ippm-bounces@ietf.org Fri Aug 04 05:25:06 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8vvQ-00089V-Qc; Fri, 04 Aug 2006 05:25:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8vvP-00087y-EZ for ippm@ietf.org; Fri, 04 Aug 2006 05:24:59 -0400 Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8vvN-0002B4-UC for ippm@ietf.org; Fri, 04 Aug 2006 05:24:59 -0400 Received: from [10.1.1.104] (mito.netlab.nec.de [195.37.70.39]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 044D81BAC4D; Fri, 4 Aug 2006 11:07:52 +0200 (CEST) Date: Fri, 04 Aug 2006 11:24:53 +0200 From: Juergen Quittek To: Tanja Zseby , STEPHAN Emile RD-CORE-LAN , ipfix@net.doit.wisc.edu, psamp@ops.ietf.org Subject: RE: [ippm] IPFIX AS /IPPM Message-ID: <809BB90D0EA0BBC110FB8FEE@[10.1.1.104]> In-Reply-To: <804B13F8F3D94A4AB18B9B01ACB68FA12534D3@EXCHSRV.fokus.fraunhofer.de> References: <804B13F8F3D94A4AB18B9B01ACB68FA12534D3@EXCHSRV.fokus.fraunhofer.de> X-Mailer: Mulberry/3.1.6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Cc: ippm@ietf.org X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ippm-bounces@ietf.org Hi Tanja, --On 02.08.2006 10:35 Uhr +0200 Tanja Zseby wrote: > Hi Emile, > > the IPPM RFCs are already mentioned in section 2.5. in version 09 of the docuemnt. > Using the IANA numbers from the IPPM registry sound like a good idea. > Does this mean that we probably could use the IANA numbers for the metrics > directly as element identifier for the IPFIX information elements? > J=FCrgen, is this possible with the IPFIX info model? e.g. using ianaIppmMetrics > in the same way as an enterprise ID? This would be an option to be considered. However, the IANA numbers identify metrics, not results from measurements according to a metric. We would have to investigate whether or not a one-to-one mapping from metric identifier to an information element carrying measured results would make sense. There might be a need to have more than one information element for a single metrics, for example, when time is measured. In the current information model we have different elements for reporting the same time information with different precisions (nanoseconds, microseconds, milliseconds, seconds). Anyway, it looks like a useful task to specify IPFIX information elements for reporting measurements according to IPPM metrics. Which numbers to assign to these elements would be just one issue to be solved within this task. Thanks, Juergen > Regards, > Tanja > > >> -----Original Message----- >> From: STEPHAN Emile RD-CORE-LAN [mailto:emile.stephan@orange-ft.com] >> Sent: Friday, July 28, 2006 4:40 PM >> To: ipfix@net.doit.wisc.edu; psamp@ops.ietf.org >> Cc: ippm@ietf.org >> Subject: [ippm] IPFIX AS /IPPM >> >> Hi, >> >> I reread IPFIX AS regarding IPPM aspects. >> >> I think that it (section 2.5) may refer to the RFCs which >> define the IPPM metrics presented. >> >> As IPFIX (section 2.7) can also be used to transfer metrics >> result I consider that the Applicability Statement has to >> propose to transfer the result conjointly with its >> corresponding metric identifier in the IANA IPPM registry >> (http://www.iana.org/assignments/ianaippmmetricsregistry-mib). >> >> Note that the draft >> http://tools.ietf.org/wg/ippm/draft-ietf-ippm-multimetrics/ >> includes pure passive metrics. So there will be metric >> identifiers for passive metrics in the IANA IPPM metrics registry. >> >> >> Regards >> Emile >> >> >> >> _______________________________________________ >> ippm mailing list >> ippm@ietf.org >> https://www1.ietf.org/mailman/listinfo/ippm >> >> > > _______________________________________________ > ippm mailing list > ippm@ietf.org > https://www1.ietf.org/mailman/listinfo/ippm _______________________________________________ ippm mailing list ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm From ippm-bounces@ietf.org Fri Aug 04 05:43:23 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8wCz-00089X-Cj; Fri, 04 Aug 2006 05:43:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8wCy-000894-Ug for ippm@ietf.org; Fri, 04 Aug 2006 05:43:08 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8wCy-00044h-RY for ippm@ietf.org; Fri, 04 Aug 2006 05:43:08 -0400 Received: from mailhub.fokus.fraunhofer.de ([193.174.154.14]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G8w5p-0002yq-5B for ippm@ietf.org; Fri, 04 Aug 2006 05:35:47 -0400 Received: from EXCHSRV.fokus.fraunhofer.de (bohr [10.147.9.231]) by mailhub.fokus.fraunhofer.de (8.11.6p2/8.11.6) with SMTP id k749Z8b15351; Fri, 4 Aug 2006 11:35:08 +0200 (MEST) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [ippm] IPFIX AS /IPPM Date: Fri, 4 Aug 2006 11:35:44 +0200 Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA12535AC@EXCHSRV.fokus.fraunhofer.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ippm] IPFIX AS /IPPM Thread-Index: Aca3p+m7NMGYSvSlSp2LH3U5cEKCCgAARVNw From: "Tanja Zseby" To: "Juergen Quittek" , "STEPHAN Emile RD-CORE-LAN" , , X-Spam-Score: -2.2 (--) X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813 Cc: ippm@ietf.org X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ippm-bounces@ietf.org Hi J=FCrgen, in our IPIFX implementation we already have defined some (vendor = specific) IEs for reporting QoS metrics. We are working on a short = technical report on this. So we could provide the descriptions of the = QoS IEs. =20 Regards, Tanja =20 > -----Original Message----- > From: Juergen Quittek [mailto:quittek@netlab.nec.de]=20 > Sent: Friday, August 04, 2006 11:25 AM > To: Tanja Zseby; STEPHAN Emile RD-CORE-LAN;=20 > ipfix@net.doit.wisc.edu; psamp@ops.ietf.org > Cc: ippm@ietf.org > Subject: RE: [ippm] IPFIX AS /IPPM >=20 > Hi Tanja, >=20 > --On 02.08.2006 10:35 Uhr +0200 Tanja Zseby wrote: >=20 > > Hi Emile, > > > > the IPPM RFCs are already mentioned in section 2.5. in=20 > version 09 of the docuemnt. > > Using the IANA numbers from the IPPM registry sound like a=20 > good idea. > > Does this mean that we probably could use the IANA numbers for the=20 > > metrics directly as element identifier for the IPFIX=20 > information elements? > > J=FCrgen, is this possible with the IPFIX info model? e.g. using=20 > > ianaIppmMetrics in the same way as an enterprise ID? >=20 > This would be an option to be considered. However, the IANA=20 > numbers identify metrics, not results from measurements=20 > according to a metric. We would have to investigate whether=20 > or not a one-to-one mapping from metric identifier to an=20 > information element carrying measured results would make sense. >=20 > There might be a need to have more than one information=20 > element for a single metrics, for example, when time is=20 > measured. In the current information model we have different=20 > elements for reporting the same time information with=20 > different precisions (nanoseconds, microseconds,=20 > milliseconds, seconds). >=20 > Anyway, it looks like a useful task to specify IPFIX=20 > information elements for reporting measurements according to=20 > IPPM metrics. Which numbers to assign to these elements=20 > would be just one issue to be solved within this task. >=20 > Thanks, >=20 > Juergen >=20 > > Regards, > > Tanja > > > > > >> -----Original Message----- > >> From: STEPHAN Emile RD-CORE-LAN=20 > [mailto:emile.stephan@orange-ft.com] > >> Sent: Friday, July 28, 2006 4:40 PM > >> To: ipfix@net.doit.wisc.edu; psamp@ops.ietf.org > >> Cc: ippm@ietf.org > >> Subject: [ippm] IPFIX AS /IPPM > >> > >> Hi, > >> > >> I reread IPFIX AS regarding IPPM aspects. > >> > >> I think that it (section 2.5) may refer to the RFCs which=20 > define the=20 > >> IPPM metrics presented. > >> > >> As IPFIX (section 2.7) can also be used to transfer=20 > metrics result I=20 > >> consider that the Applicability Statement has to propose=20 > to transfer=20 > >> the result conjointly with its corresponding metric=20 > identifier in the=20 > >> IANA IPPM registry=20 > >> (http://www.iana.org/assignments/ianaippmmetricsregistry-mib). > >> > >> Note that the draft > >> http://tools.ietf.org/wg/ippm/draft-ietf-ippm-multimetrics/ > >> includes pure passive metrics. So there will be metric identifiers=20 > >> for passive metrics in the IANA IPPM metrics registry. > >> > >> > >> Regards > >> Emile > >> > >> > >> > >> _______________________________________________ > >> ippm mailing list > >> ippm@ietf.org > >> https://www1.ietf.org/mailman/listinfo/ippm > >> > >> > > > > _______________________________________________ > > ippm mailing list > > ippm@ietf.org > > https://www1.ietf.org/mailman/listinfo/ippm >=20 >=20 >=20 _______________________________________________ ippm mailing list ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm From ippm-bounces@ietf.org Fri Aug 04 09:05:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8zMU-0000na-KM; Fri, 04 Aug 2006 09:05:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8zMT-0000nS-3X for ippm@ietf.org; Fri, 04 Aug 2006 09:05:09 -0400 Received: from mail120.messagelabs.com ([216.82.250.83]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G8zMQ-0004lc-Of for ippm@ietf.org; Fri, 04 Aug 2006 09:05:09 -0400 X-VirusChecked: Checked X-Env-Sender: acmorton@att.com X-Msg-Ref: server-2.tower-120.messagelabs.com!1154696705!12377941!1 X-StarScan-Version: 5.5.10.7; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 26729 invoked from network); 4 Aug 2006 13:05:05 -0000 Received: from unknown (HELO maillennium.att.com) (134.24.146.4) by server-2.tower-120.messagelabs.com with SMTP; 4 Aug 2006 13:05:05 -0000 Received: from acmt.att.com (acmt.mt.att.com[135.16.251.41](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20060804130505gw1003joqfe>; Fri, 4 Aug 2006 13:05:05 +0000 Message-Id: <6.2.1.2.0.20060804084707.071b8c28@postoffice.maillennium.att.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Fri, 04 Aug 2006 09:05:05 -0400 To: Juergen Quittek , Tanja Zseby , STEPHAN Emile RD-CORE-LAN , ipfix@net.doit.wisc.edu,psamp@ops.ietf.org From: Al Morton Subject: RE: [ippm] IPFIX AS /IPPM In-Reply-To: <809BB90D0EA0BBC110FB8FEE@[10.1.1.104]> References: <804B13F8F3D94A4AB18B9B01ACB68FA12534D3@EXCHSRV.fokus.fraunhofer.de> <809BB90D0EA0BBC110FB8FEE@[10.1.1.104]> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Cc: ippm@ietf.org X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ippm-bounces@ietf.org At 05:24 AM 8/4/2006, Juergen Quittek wrote: >>--On 02.08.2006 10:35 Uhr +0200 Tanja Zseby wrote: >> >>Hi Emile, >> >>the IPPM RFCs are already mentioned in section 2.5. in version 09 of the= =20 >>docuemnt. >>Using the IANA numbers from ... >>...snip... >>J=FCrgen, is this possible with the IPFIX info model? e.g. using=20 >>ianaIppmMetrics >>in the same way as an enterprise ID? > >This would be an option to be considered. However, the IANA numbers= identify >metrics, not results from measurements according to a metric. We would=20 >have to >investigate whether or not a one-to-one mapping from metric identifier to= an >information element carrying measured results would make sense. Depending on the options selected for some metrics, like delay variation, even the metric itself can be completely different from another instance with alternative options. >There might be a need to have more than one information element >for a single metrics, for example, when time is measured. All the IPPM metrics have a set of parameters that allow one to specify the variable aspects of the metric (e.g., Poisson or Periodic stream and all their stream variables, Loss waiting time threshold). Somehow, these need to be linked to the results, or they will loose their meaning. This is an issue for IPPM's existing registry. Al >In the current >information model we have different elements for reporting the same time >information with different precisions (nanoseconds, microseconds, >milliseconds, seconds). _______________________________________________ ippm mailing list ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm From juhua1128@tom.com Fri Aug 11 04:40:55 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GBSZb-0004rH-0F for ippm-archive@lists.ietf.org; Fri, 11 Aug 2006 04:40:55 -0400 Received: from [61.144.147.128] (helo=tom.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBSZI-00012T-OI for ippm-archive@lists.ietf.org; Fri, 11 Aug 2006 04:40:54 -0400 Received: from WEI-FFB93D71FEB[192.168.1.100] by tom.com with SMTP id 2CE44964; Fri, 11 Aug 2006 16:40:27 +0800 From: "fair" Subject: CHIFA To: "ippm-archive" Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: 8bit Reply-To: weixin1028@126.com Date: Fri, 11 Aug 2006 16:40:34 +0800 X-Mailer: FoxMail 4.0 beta 2 [cn] X-Spam-Score: 4.8 (++++) X-Scan-Signature: 489500194134bea022a3070ad86cad76 The 10th China (Guangzhou) International Factory Automation & Instrument Exhibition

 

The 11th China (Guangzhou) International Factory Automation & Instrument Exhibition

 

March 7- 10, 2007

Chinese Export Commodities Fair Pazhou Complex

Guangzhou, China

 

 

 

Guangzhou --- The Hub of the Automation Industry

Guangzhou is located in the central area of the Pearl River Delta, which is the most active and fast-developing economic region in China. As the largest central city in this area, Guangzhou has an active flow of human resources, materials logistics, capital and information. With its solid economic power, convenient traffic networks, huge consumer market, well-developed exhibition services and socialized exhibition system, Guangzhou is no doubt the ideal place for holding international exhibitions.

 

 

A Market with a Great Potential

From the development of the Chinese industrial automatic market, China has the largest market in the world. But compared to the industries of developed countries, China show huge technological shortcomings in the industries of Factory Automation. Transformation of the traditional industrial technology, automation of the factory and informization of the enterprises display a strong need for foreign investment and imported high-end automation products. In 2001, demand for industrial automation products in China increased to US$20.9 billion and experts predict annual growth of more than 10% in the near future.

 

Please see below a market report of some industrial automation products from GCIS (a well-known market research company):

Products

Total Value in 2001

Total Value in 2005

Annual Growth Rate

PLC

2.14 bil.

3.4 bil.

15%

DCS

1.97 bil.

2.65 bil.

9%

IPC

1.01 bil.

1.49 bil.

12%

Idustrial Software

0.45 bil.

0.83 bil.

21%

 

 

CHIFA 2007 ------ your best choice!

CHIFA, held successfully for 10 years, is now the largest automation exhibition in South China. The exhibition area has been increased from 5,000 sqm to 17,000 sqm, and the visitors in 2006 is five times the number of that attended 1997. In 2007, over 500 exhibitors are expected to attend the show.

 

CHIFA 2007 will take place simultaneously with other 5 leading shows in China, such as Power Transmission Show, Printing Show, Sino-Pack Show, China Drinktec Show and Water Treatment Show. Harness the combined synergies generated by these 6 thematically interrelated events and reap the business opportunities for your company.

 

CHIFA show high tech products, offer up-todate information about science and technology, and symposiums are organized concurrently to attract high-ranking visitors.  It is a completely new stage and window for economic and trading cooperation to Chinese and foreign enterprises.

 

 

Exhibits Category

Robotics

Industrial Robot, Service Robot, Robot simulation and vision system，Machine, appliance and component for Robotics.

 Factory Automation

Assembly, Handling, Industrial image processing, Automatic assembly system & component, Factory automation system, Quality control.

 Process Automation

Connector and connect system，Contactor，Starter，Sensor，Converter, Regulator，Industrial Enclosure，Equipment and technique for control room，UPS, Industrial power generator, Servo motor, Electric switchgear, Air compressor and accessories.

Automation Technology & Solutions

Industrial automation solutions，Solutions for Production, Planning and control，Solutions for manufacturing execution system and advanced process control and etc.

Instruments and Meters

Sensors and measuring devices, Weighing systems, Analyzers, Positioners, Module and auxiliary equipment，Electric measuring instrument，quality control and measuring equipment.

 Control System

Industrial Ethernet and Fieldbus technology and equipment，Security Automation，Process control system/DCS，PLC，PC-based automation，Industrial control computer，Industrial power supply，Human machine interface, Controller and special purpose control system.

 

 

For Enquiry:

China Foreign Trade Guangzhou Exhibition Corp.

Add: No. 117 Liuhua Road, Guangzhou 510014, China

Tel:  0086-20- 85671373, 26081669

Fax:  0086-20- 85681273, 86663416-02

E-mail:weixin1028@sina.com

Contact Person: yuan xin  wei  

 

 

APPLICATION FORM

Company:                                                                                     

Address:                                                                                      

Tel:                             Fax:                        Contact person (Mr./Ms)            

Title:                            E-mail:                     Website:                          

Nature of Business:

Manufacturer□ Wholesaler□ Distributor□ Importer Agent□ Publisher□ Other□

Products                                                                       

According to the Regulations of CHIFA , we apply for

 

 

Booths

Shell Scheme booth (9 m2)

Raw Space

Unite Price

Quantity

 

Total Cost

USD2300

□

USD230/m2□

 

 

 

 

Advertising

In catalogue

Front Cover

 

Back cover

 

Inside Front Cover

Inside Page

Total Cost

USD2500□

USD2000□

 

USD1000□

 

USD850□

 

 

Remarks :

■The basic design for each shell scheme booth (3m x 3m)consist of : wall panels ,fascia board ,one square table, two folding chairs, two fluorescent lamps, carpet and wastebasket ,etc.

■Raw space rent at least 36m2 with free list in the official catalogue

■      The photocopied or faxed Form is equivalent to the original .

■      Please tick “√ “where required.

Please send the application forms with 50% of the payment to:

Account: China Foreign Trade Guangzhou Exhibition Corp.

ACCN NO: 800103271008095014

Bank: Bank of China Guangdong Branch

Bank Add. : 197 Dongfengxi Rd., Guangzhou, China

 

Signature:                                 Date:                         

With Company Stamp

 

From ippm-bounces@ietf.org Fri Aug 11 16:54:20 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GBe19-0000EO-RI; Fri, 11 Aug 2006 16:54:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GBe18-0000EJ-OW for ippm@ietf.org; Fri, 11 Aug 2006 16:54:06 -0400 Received: from basie.internet2.edu ([207.75.164.22]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBe17-00010L-Hr for ippm@ietf.org; Fri, 11 Aug 2006 16:54:06 -0400 Received: from localhost (localhost [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 55E4447C72; Fri, 11 Aug 2006 16:54:05 -0400 (EDT) Received: from basie.internet2.edu ([127.0.0.1]) by localhost (basie.internet2.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06799-03; Fri, 11 Aug 2006 16:54:05 -0400 (EDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 38BA247C1B; Fri, 11 Aug 2006 16:54:05 -0400 (EDT) Message-ID: <44DCEE6C.1090605@internet2.edu> Date: Fri, 11 Aug 2006 16:54:04 -0400 From: Matthew J Zekauskas User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: ippm@ietf.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by mail.internet2.edu virus scanner X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Cc: Henk Uijterwaal , Matt Zekauskas Subject: [ippm] draft minutes up X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ippm-bounces@ietf.org There are some notes on paper I need to make sure are reflected in items 6a and 6b. If you have any comments, feel free to send them to the chairs or the list. --Matt _______________________________________________ ippm mailing list ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm From ippm-bounces@ietf.org Tue Aug 22 12:40:55 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFZGz-0004An-9S; Tue, 22 Aug 2006 12:38:41 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFZGx-0004AV-N9 for ippm@ietf.org; Tue, 22 Aug 2006 12:38:39 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFWUL-0006Q1-HI for ippm@ietf.org; Tue, 22 Aug 2006 09:40:17 -0400 Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GFW8T-00071t-6a for ippm@ietf.org; Tue, 22 Aug 2006 09:17:45 -0400 Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 Aug 2006 15:16:31 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [ippm] IPFIX AS /IPPM Date: Tue, 22 Aug 2006 15:16:29 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ippm] IPFIX AS /IPPM Thread-Index: Aca3xpyDcDyRT4quTIyMI1JMCncYsAOA7hwg From: "STEPHAN Emile RD-CORE-LAN" To: "Al Morton" , "Juergen Quittek" , "Tanja Zseby" , , X-OriginalArrivalTime: 22 Aug 2006 13:16:31.0504 (UTC) FILETIME=[2F1DC900:01C6C5ED] X-Spam-Score: -2.6 (--) X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6 Cc: ippm@ietf.org X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ippm-bounces@ietf.org Dear all, It is obvious that reporting metrics measurement results need much more = information that an identifier of the metric. Nevertheless the usage of = a measurement result requires the presence of 2 pieces of information = 'what is measured? 'and 'how it was measured?'. By now IPFIX data model does not provide anything to couple measurement = described in draft-ietf-ipfix-as-10.txt and IPPM metrics. So to get a = standard mapping between IPPM metrics definitions and measurements = (IPFIX or IPPM ones) it is urgent to define IEs to say 'what is = measured?' and 'how it was measured?':=20 Name: ianaIppmMetricsIdentifier Description: The identifier of a metric as per = http://www.iana.org/assignments/ianaippmmetricsregistry-mib . Abstract Data Type: integer Data Type Semantics: identifier Name: metricMeasurementMethod Description: The measurement method (NDLR: add description and = ref to IPPM, IPFIX and PSAMP RFC which define the methods) Abstract Data Type: integer Data Type Semantics: enum { passive, periodic, poisson ... } Name: measurementId Description: The identifier of one measure Abstract Data Type: integer Data Type Semantics: identifier My thinking is that we have to define now with these IE firstly to reach = a minimal level of interoperability of IPFIX measurement information as = per IPFIX AS and finally to couple definitively passive and active = measurement methods. I agree that measurement methods and metrics have specific parameters = that are not addressed by = http://www.iana.org/assignments/ianaippmmetricsregistry-mib. So I = started the definition of a reporting registry = (http://tools.ietf.org/wg/ippm/draft-stephan-ippm-reporting-registry-00.t= xt ) to register progressively the specific set of parameters to report = per metric application. Based on IPPM WG works on composition, = aggregation and reporting this registry will gather protocol neutral set = of parameters to report that should be used any data model.=20 To sum up, I propose to add now the 3 IE above in the IPFIX/PSAMP data = model; then I suggest completing the definition of the set of parameters = of several metrics usage in the ippm reporting registry before San Diego = meeting; there we might present their usage using IPFIX data model in a = IPPM/PSAMP/IPFIX common meeting. Regards Emile > -----Message d'origine----- > De=A0: Al Morton [mailto:acmorton@att.com] > Envoy=E9=A0: vendredi 4 ao=FBt 2006 15:05 > =C0=A0: Juergen Quittek; Tanja Zseby; STEPHAN Emile RD-CORE-LAN; > ipfix@net.doit.wisc.edu; psamp@ops.ietf.org > Cc=A0: ippm@ietf.org > Objet=A0: RE: [ippm] IPFIX AS /IPPM >=20 > At 05:24 AM 8/4/2006, Juergen Quittek wrote: > >>--On 02.08.2006 10:35 Uhr +0200 Tanja Zseby wrote: > >> > >>Hi Emile, > >> > >>the IPPM RFCs are already mentioned in section 2.5. in version 09 of = the > >>docuemnt. > >>Using the IANA numbers from ... > >>...snip... > >>J=FCrgen, is this possible with the IPFIX info model? e.g. using > >>ianaIppmMetrics > >>in the same way as an enterprise ID? > > > >This would be an option to be considered. However, the IANA numbers > identify > >metrics, not results from measurements according to a metric. We = would > >have to > >investigate whether or not a one-to-one mapping from metric = identifier to > an > >information element carrying measured results would make sense. >=20 > Depending on the options selected for some metrics, like > delay variation, even the metric itself can be completely > different from another instance with alternative options. >=20 >=20 > >There might be a need to have more than one information element > >for a single metrics, for example, when time is measured. >=20 > All the IPPM metrics have a set of parameters that allow one to = specify > the variable aspects of the metric (e.g., Poisson or Periodic > stream and all their stream variables, Loss waiting time threshold). > Somehow, these need to be linked to the results, or they will > loose their meaning. This is an issue for IPPM's existing registry. >=20 > Al >=20 > >In the current > >information model we have different elements for reporting the same = time > >information with different precisions (nanoseconds, microseconds, > >milliseconds, seconds). _______________________________________________ ippm mailing list ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm From ippm-bounces@ietf.org Wed Aug 30 18:58:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GIYzC-0004yS-Ar; Wed, 30 Aug 2006 18:56:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GIYz9-0004y1-29; Wed, 30 Aug 2006 18:56:39 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GIWL3-00028B-1a; Wed, 30 Aug 2006 16:07:05 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GIW5a-00018Z-GR; Wed, 30 Aug 2006 15:51:13 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 738EA17627; Wed, 30 Aug 2006 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GIW4Y-0003hD-19; Wed, 30 Aug 2006 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 30 Aug 2006 15:50:02 -0400 X-Spam-Score: -5.9 (-----) X-Scan-Signature: 386e0819b1192672467565a524848168 Cc: ippm@ietf.org Subject: [ippm] I-D ACTION:draft-ietf-ippm-storetraceroutes-01.txt X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ippm-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Performance Metrics Working Group of the IETF. Title : Traceroute Measurements Information Model and XML Data Model Author(s) : S. Niccolini, et al. Filename : draft-ietf-ippm-storetraceroutes-01.txt Pages : 45 Date : 2006-8-30 This memo describes a standard way to store traceroute measurements. To better address the traceroute measurements storing issue, the authors first of all give a definition of the traceroute tool, describe the tool itself as well as its parameters and the default values on the most common operating systems and the output results that can be stored. Afterwards, the common information model with the base elements of the traceroute measurement storing is defined dividing the information elements in two semantically separated groups (configuration elements and results ones). Moreover an additional element is defined to relate configuration elements and results ones by means of a common unique identifier. On the basis of the information model a data model is then proposed in order to actually store the traceroute measurements. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ippm-storetraceroutes-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ippm-storetraceroutes-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ippm-storetraceroutes-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-8-30140741.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ippm-storetraceroutes-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ippm-storetraceroutes-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-8-30140741.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ippm mailing list ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm --NextPart-- From ippm-bounces@ietf.org Thu Aug 31 09:21:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GImRS-0004NC-TO; Thu, 31 Aug 2006 09:18:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GImRR-0004N7-IG for ippm@ietf.org; Thu, 31 Aug 2006 09:18:45 -0400 Received: from smtp0.netlab.nec.de ([195.37.70.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GImRP-0006Ek-0j for ippm@ietf.org; Thu, 31 Aug 2006 09:18:45 -0400 Received: from localhost (localhost.office [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id C94DB200C8E1 for ; Thu, 31 Aug 2006 15:19:07 +0200 (CEST) Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25185-01 for ; Thu, 31 Aug 2006 15:19:07 +0200 (CEST) Received: from mx1.office (mx1.office [10.1.1.23]) by smtp0.netlab.nec.de (Postfix) with ESMTP id A44B320031DB for ; Thu, 31 Aug 2006 15:19:07 +0200 (CEST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C6CCFF.FAACCE46" X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Thu, 31 Aug 2006 15:18:41 +0200 Message-ID: X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: I-D ACTION:draft-ietf-ippm-storetraceroutes-01.txt Thread-Index: AcbMh9ZPi2Tc5Q+TT+GoyixQncv0uAAd8wQg From: "Saverio Niccolini" To: X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office) X-Spam-Score: 0.0 (/) X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c Cc: Subject: [ippm] FW: I-D ACTION:draft-ietf-ippm-storetraceroutes-01.txt X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ippm-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C6CCFF.FAACCE46 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, as promised we just submitted a new version of the traceroute draft including the differences to DISMAN RFC4560. Please have a look at it and send comments if you like. Cheers, Saverio > -----Original Message----- > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20 > Posted At: Wednesday, August 30, 2006 9:50 PM > Posted To: announce-IDs > Conversation: I-D ACTION:draft-ietf-ippm-storetraceroutes-01.txt=20 > Subject: I-D ACTION:draft-ietf-ippm-storetraceroutes-01.txt=20 >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts=20 > directories. > This draft is a work item of the IP Performance Metrics=20 > Working Group of the IETF. >=20 > Title : Traceroute Measurements Information=20 > Model and XML Data Model > Author(s) : S. Niccolini, et al. > Filename : draft-ietf-ippm-storetraceroutes-01.txt > Pages : 45 > Date : 2006-8-30 > =09 > This memo describes a standard way to store traceroute measurements. > To better address the traceroute measurements storing issue, the > authors first of all give a definition of the traceroute tool, > describe the tool itself as well as its parameters and the default > values on the most common operating systems and the output results > that can be stored. Afterwards, the common information model with > the base elements of the traceroute measurement storing is defined > dividing the information elements in two semantically separated > groups (configuration elements and results ones). Moreover an > additional element is defined to relate configuration elements and > results ones by means of a common unique identifier. On the basis of > the information model a data model is then proposed in order to > actually store the traceroute measurements. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ippm-storetrace routes-01.txt >=20 > To remove yourself from the I-D Announcement list, send a message to=20 > i-d-announce-request@ietf.org with the word unsubscribe in=20 > the body of=20 > the message.=20 > You can also visit=20 > https://www1.ietf.org/mailman/listinfo/I-D-announce=20 > to change your subscription settings. >=20 > Internet-Drafts are also available by anonymous FTP. Login with the=20 > username "anonymous" and a password of your e-mail address. After=20 > logging in, type "cd internet-drafts" and then=20 > "get draft-ietf-ippm-storetraceroutes-01.txt". >=20 > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html=20 > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-ietf-ippm-storetraceroutes-01.txt". > =09 > 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=20 > 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. >=20 > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. >=20 ------_=_NextPart_001_01C6CCFF.FAACCE46 Content-Type: application/octet-stream; name="ATT256475.TXT" Content-Transfer-Encoding: base64 Content-Description: ATT256475.TXT Content-Disposition: attachment; filename="ATT256475.TXT" Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl cnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBlOiB0ZXh0 L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNi04LTMwMTQwNzQxLkktREBpZXRmLm9yZz4NCg0KRU5D T0RJTkcgbWltZQ0KRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtaXBwbS1zdG9yZXRy YWNlcm91dGVzLTAxLnR4dA0K ------_=_NextPart_001_01C6CCFF.FAACCE46 Content-Type: application/octet-stream; name="draft-ietf-ippm-storetraceroutes-01.URL" Content-Transfer-Encoding: base64 Content-Description: draft-ietf-ippm-storetraceroutes-01.URL Content-Disposition: attachment; filename="draft-ietf-ippm-storetraceroutes-01.URL" W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0 cy9kcmFmdC1pZXRmLWlwcG0tc3RvcmV0cmFjZXJvdXRlcy0wMS50eHQNCg== ------_=_NextPart_001_01C6CCFF.FAACCE46 Content-Type: text/plain; name="ATT256476.txt" Content-Transfer-Encoding: base64 Content-Description: ATT256476.txt Content-Disposition: attachment; filename="ATT256476.txt" X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo= ------_=_NextPart_001_01C6CCFF.FAACCE46 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ippm mailing list ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm ------_=_NextPart_001_01C6CCFF.FAACCE46--