From mailnull@www1.ietf.org  Tue Apr  1 09:10:24 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12207
	for <trigtran-archive@odin.ietf.org>; Tue, 1 Apr 2003 09:10:24 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h31EYBK11705
	for trigtran-archive@odin.ietf.org; Tue, 1 Apr 2003 09:34:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h31EYBK11702
	for <trigtran-web-archive@optimus.ietf.org>; Tue, 1 Apr 2003 09:34:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12132
	for <trigtran-web-archive@ietf.org>; Tue, 1 Apr 2003 09:09:53 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h31EY4K11510;
	Tue, 1 Apr 2003 09:34:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h31EX2K11328
	for <trigtran@optimus.ietf.org>; Tue, 1 Apr 2003 09:33:02 -0500
Received: from netsgo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA12054;
	Tue, 1 Apr 2003 09:08:40 -0500 (EST)
From: wwxooicuy@netsgo.com
Message-ID: <6ad8399b65c1$1aa5a4c3$d15dd4fa@qgrespvrd.rwm>
To: <gbk1b9d02350@ietf.org>
Cc: <chess_world@ietf.org>, <trigtran@ietf.org>
Date: Tue, 01 Apr 2003 09:51:09 +0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_FB7_D345_8555AAA5.3624960B"
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
Subject: [Trigtran] Re: 지역, 성별, 나이로 분류된 이멜리스트를 소개합니다
Sender: trigtran-admin@ietf.org
Errors-To: trigtran-admin@ietf.org
X-BeenThere: trigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=unsubscribe>
List-Id: Triggers for Transport <trigtran.ietf.org>
List-Post: <mailto:trigtran@ietf.org>
List-Help: <mailto:trigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=subscribe>

------=_NextPart_FB7_D345_8555AAA5.3624960B
Content-Type: text/plain;
	charset="euc-kr"
Content-Transfer-Encoding: quoted-printable


------=_NextPart_FB7_D345_8555AAA5.3624960B
Content-Type: text/html;
	charset="euc-kr"
Content-Transfer-Encoding: base64


NTY4MzI2ODY1NDcyMzIxMjQ1MjY4MDU3MDcyNzc2NTg3MTY0ODc2NTI2NTUz
NjAxNDYzIDUyMDcgS1JFSUFMUlNEVFVJVEhEV1kgUzcga2lxY211ZTMxMjQ4
NDgzMTY4ODUwODAyNzczNjQwMDI1NzU1NzExNzA0MTA1MjEzNDIxNDQ2ODQ1
NTMzNDU1MzM3NjgyMjczMjExODA0MTIyIDAwMjM4IFZPVEZTQk1TIGI1MTEg
ZmJsaGlnZHV2c3Zvcm9oDQo8aHRtbD4NCjxib2R5Pjxmb250IGZhY2U9IrW4
v/Istbi/8sO8Ij4NCjx0YWJsZSB3aWR0aD02NTA+DQo8dHI+PHRkPjxmb250
IGNvbG9yPXJlZCBzaXplPTQ+PGI+DQo8cD4xLiDA/LzbILy6sPi1yCDAzLjh
wda80ri4ILCht8G7zL7GILi4tem+7sH4IDi56bi4sLMgwMy44biuvbrGrijB
37q5waawxSwgx9G43sDPwaawxSk8YnI+DQoyLiDB9r+qILnXILy6urAsILOq
wMy3ziC60Lf5tcggM8O1NLnpuLiwsyDAzLjhuK69usauKMHfurnBprDFLCDH
0bjewM/BprDFKTxicj4NCjMuIMDMuOHAuyC53rTCILytufbAxyC9usbUx8rF
zbi1wLsgwN8gxeuw+sfPv6kguei03rf8wMwgs/S1tbfPIMavvPbHz7DUIMDf
IMGkuK61yCAzw7U4uem4uLCzIMDMuOG4rr26xq4owd+6ucGmsMUsIMfRuN7A
z8GmsMUpPGJyPg0KNC4gx9G43sDPIMHWvNK3zri4ILG4vLq1x77uwfggx9G4
3sDPIMDMuOG4rr26xq4gw7U1uem4uLCzKMHfurnBprDFKTwvZm9udD48L3A+
DQo8cD48Yj48Zm9udCBzaXplPTQ+wMy6pcauIMfVtM+02S4gseKwozogNL/5
IDEwwM+x7sH2LiDAzLqlxq4gxNq15TogR0tJRzwvZm9udD48YnI+DQo8Zm9u
dCBzaXplPTQ+wMy6pcauMTwvZm9udD46IDxmb250IGNvbG9yPWdyZWVuIHNp
emU9ND7AzLqlxq4gseLH0bO7v6EgwMy44biuvbrGrrimILG4wNTHz73DtMIg
utCysrTCIDIwMLi4xesgud+827Trx+Aguau34SDH/cXDwLsgteW4s7TPtNku
IMDMuOG4rr26xq6/zSC537zbtOvH4MDHIMf9xcPAuyC1v73Dv6EgtKm4sSC8
9iDA1rTCIMDMILHiyLi4piCz9cShwfYguLa9w7HiILnZtvi0z7TZLijAzLjh
uK69usauILG4wNTIxCwgsO2wtMDHILnfvNsgtckgwMy44bO7v+u4uCC6uLO7
wda9w7jpILXLtM+02S4gvPa9xbDFus4gtsfH0SDA+sjxsKEgwNrDvMD7wLi3
ziDH2LXluK6x4iC2p7muv6EgvPa9xbDFus64piDH0sHZILjwuKO9w7T1tvO1
tSDA/Mf0ILDGwaTHz73HIMfKv+S++L3AtM+02S4gwNrDvCDAzsXNs90gtvPA
zrD6ILjewM+8rbn2uKYgyK7D5sfPv6kgwMwguPC157DNwMwgsKG0ycfYwbO9
wLTPtNkuKSC8usDOsPy3w8DMuOGw+iDHx7bzucy15bjewM+wsMC6ILrSuf24
3sDPwLoguau34bnfvNu068fgv6Egx9i058DMIL7Itcu0z7TZLjwvZm9udD48
YnI+DQo8Zm9udCBzaXplPTQ+wMy6pcauMjwvZm9udD46IDxmb250IGNvbG9y
PWdyZWVuIHNpemU9ND7AzLqlxq4gseLH0bO7v6EgwMy44biuvbrGriCxuMDU
x8+9w7jpILnfvNux4ijH0bjewM+537zbseK0ySzAzLjhuK69usauIMGkuK6x
4rTJW8bEwM+60MfSseK0ySDG98fUXSy89r3FsMW6zsOzuK6x4rTJLLr8uKUg
ud+82yyx17iywLsgwMy/68fRIMDavLzH0SC1tb/yuLtbwMy44bi2xMnGwyDD
s8C9IL3DwNvHz73DtMIgutC1tSC757/rsKG0yV0ptbUgsLDAzCC15biztM+0
2S4gv6m3r7TrwMcgxMTHu8XNv6Egtb+9wyC757/rsKG0ycfVtM+02S48L2I+
PC9mb250PjwvcD4NCg0KPHA+PGZvbnQgY29sb3I9Ymx1ZSBzaXplPTQ+PGI+
wKcgPHU+NLChwfYgwMy44biuvbrGrjwvdT4ow9EgOTUwMLi4sLMgwMy44cHW
vNIpILjwtc64piA8Zm9udCBjb2xvcj1yZWQ+x8+zqrfOILmtvu68rSAxNbi4
v/i/oTwvZm9udD4gxse4xcfVtM+02S4gwPy827y6sPggOLnpuLiwsyDAzLjh
uK69usauwMcgud+827f8wMwgNTAlwMzHz7fOILOqv8MgsOa/7CDIr7rSx9gg
teW4rrDavcC0z7TZLjxicj48YnI+DQq6uLTZIMDavLzH0SCzu7/rsPogwda5
rrnmuf3AuyC+y7DtIL3NwLi9w7jpICA8YSBocmVmPSJtYWlsdG86a29yZWFy
dWxlc0BuYXZlci5jb20iPmtvcmVhcnVsZXNAbmF2ZXIuY29tPC9hPiDAuLfO
ILmuwMfH2MHWvcO46SC1y7TPtNkuILmuwMe9wyC8usfUL7+stvTDs7imILOy
seK9w7jpILChwOUgu6G4riDDs7iux9ggteW4rrDavcC0z7TZLiC5rsDHx8+9
xyC2pyDAzLqlxq4gxNq15bimIL7Lt8Egwda8xb7fIMDMuqXGriDH/cXDwLsg
ud7AuL3HILz2IMDWvcC0z7TZLjwvYj48L2ZvbnQ+PC9wPg0KDQo8cD48Zm9u
dCBjb2xvcj1yZWQgc2l6ZT00PjxiPr3RuMC/oSA1uLi/+MKluK4gwMy44biu
vbrGrrimILG4wNTHz73DsO0gvrK3ubHiw7O3syC+tbjwvvi02bTCILvnvce/
oSCz7rbzvcUgutC16SC4ucC4vceyrrTPtNkuILHXt7EgwMy44biuvbrGriC6
2cDisO0gveLI98DatM8gvsax9bDtILnfvNvHz8DatM8gwdewrLTZsO0gtMCz
or3HILKutM+02S4gsde3sSC60LXpwLogwPrI8cDHIMDMuOG4rr26xq64piCw
ocH2sO0gtNm9wyC/+LHiuKYgyLi6ucfPvcOx5iC52bb4tM+02S4gyKu6uLTC
ILvnvvfAxyC/+LW/t8LA1LTPtNkuIMirurjA2sO8uKYgxvex4sfSILz4IL74
tMIgwM/A1LTPtNkuILvnvvfHz73DtMIgtNS16SwgyK3AzMbDISE8L2I+PC9m
b250PjwvcD4NCg0KPHA+wMwguN7Az8C6IMi4vcXAzCC1x8H2IL7KvcC0z7TZ
LiC89r3FsMW6zrTCIDxhIGhyZWY9Im1haWx0bzprb3JlYXJ1bGVzQG5hdmVy
LmNvbT9zdWJqZWN0Pbz2vcWwxbrOIj6/qbHiPC9hPrimIMWsuK/H2CDB1ry8
v+QuPC9wPg0KPHA+SWYgeW91IHByZWZlciBub3QgdG8gcmVjZWl2ZSBmdXJ0
aGVyIGUtbWFpbHMgb2YgdGhpcyB0eXBlIGZyb20gdXMsIHBsZWFzZSA8YSBo
cmVmPSJtYWlsdG86a29yZWFydWxlc0BuYXZlci5jb20/c3ViamVjdD1SRU1P
VkUiPkNsaWNrIGhlcmU8L2E+PC9wPjxicj48L3RkPjwvdHI+PC90YWJsZT4N
CjwvZm9udD4NCjwvYm9keT4NCjwvaHRtbD4=

------=_NextPart_FB7_D345_8555AAA5.3624960B--

_______________________________________________
Trigtran mailing list
Trigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/trigtran



From mailnull@www1.ietf.org  Sun Apr  6 08:26:36 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26537
	for <trigtran-archive@odin.ietf.org>; Sun, 6 Apr 2003 08:26:36 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h36CUJs07130
	for trigtran-archive@odin.ietf.org; Sun, 6 Apr 2003 08:30:19 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h36CUJ807126
	for <trigtran-web-archive@optimus.ietf.org>; Sun, 6 Apr 2003 08:30:19 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26533
	for <trigtran-web-archive@ietf.org>; Sun, 6 Apr 2003 08:26:04 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h36CUC807118;
	Sun, 6 Apr 2003 08:30:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h36CTJ807077
	for <trigtran@optimus.ietf.org>; Sun, 6 Apr 2003 08:29:19 -0400
Received: from naver.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA26525;
	Sun, 6 Apr 2003 08:24:55 -0400 (EDT)
From: ttdsscbfm@naver.com
Message-ID: <fba57d38277f$53d21470$f30f68da@yptvxtl.p>
To: <gbk1b9d02350@ietf.org>
Cc: <chess_world@ietf.org>, <trigtran@ietf.org>
Date: Sun, 06 Apr 2003 04:17:37 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_15A_C372_4F43D4E8.AE26CBB9"
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
Subject: [Trigtran] Re: 전송성공된 이멜리스트를 원하십니까?480588025716566713318224454423255448517613406306 3 CYB lr4oqo rcmqflusclsiae
Sender: trigtran-admin@ietf.org
Errors-To: trigtran-admin@ietf.org
X-BeenThere: trigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=unsubscribe>
List-Id: Triggers for Transport <trigtran.ietf.org>
List-Post: <mailto:trigtran@ietf.org>
List-Help: <mailto:trigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=subscribe>

------=_NextPart_15A_C372_4F43D4E8.AE26CBB9
Content-Type: text/plain;
	charset="euc-kr"
Content-Transfer-Encoding: quoted-printable


------=_NextPart_15A_C372_4F43D4E8.AE26CBB9
Content-Type: text/html;
	charset="euc-kr"
Content-Transfer-Encoding: base64


NTI1NzY0NzAzNDQyNDcxMDUxNTMyMzI4MzMxNzc0MzE4MzE4ODA4MTEyMzgy
ODQ1MDY2MzM4NDA1NjA3ODAwNDEyMTU2MyAwNjA1NTMgVkFDSkxLSkdPS0RF
IHNnUjVSM3FPU0c2MDBFIGthcWZucWd0Y2Fhdms2NTQ4Mzc3MDQxNDgyODMy
NjY1NTA2NzU4MzgxNDA1MDUxMzM3MTYgMDE0NyBFTEdDWFFYTVlEU0lBRlgg
MTd4b3hQdjRJMDQ1IGliYQ0KPGh0bWw+DQo8Ym9keT48Zm9udCBmYWNlPSK1
uL/yLLW4v/LDvCI+DQo8dGFibGUgd2lkdGg9NjUwPg0KPHRyPjx0ZD48Zm9u
dCBjb2xvcj1yZWQgc2l6ZT00PjxiPg0KPHA+yL+w+iDCr8DOIDk1MDC4uLCz
IMDMuOG4rr26xq64piDGx7jFx9W0z7TZLjxicj4NCjk1MDC4uLCzIMDMuOG4
rr26xq7AxyDGr8KhsPogsbi8usC6ILTZwL2w+iCwsL3AtM+02S48YnI+DQox
LiDA/LzbILy6sPi1yCDAzLjhwda80ri4ILCht8G7zL7GILi4tem+7sH4IDi5
6bi4sLMgwMy44biuvbrGrijB37q5waawxSwgx9G43sDPwaawxSk8YnI+DQoy
LiDB9r+qILnXILy6urAsILOqwMy3ziC60Lf5tcggM8O1NLnpuLiwsyDAzLjh
uK69usauKMHfurnBprDFLCDH0bjewM/BprDFKTxicj4NCjMuIMDMuOHAuyC5
3rTCILytufbAxyC9usbUx8rFzbi1wLsgwN8gxeuw+sfPv6kguei03rf8wMwg
s/S1tbfPIMavvPbHz7DUIMDfIMGkuK61yCAzw7U4uem4uLCzIMDMuOG4rr26
xq4owd+6ucGmsMUsIMfRuN7Az8GmsMUpPGJyPg0KNC4gx9G43sDPIMHWvNK3
zri4ILG4vLq1x77uwfggw7U1uem4uLCzIMDMuOG4rr26xq4gKMHfurnBprDF
KTwvZm9udD48L3A+DQo8cD48Yj48Zm9udCBzaXplPTQ+wMy6pcauIMfVtM+0
2S4gseKwozogNL/5IDEwwM+x7sH2Ljxicj4NCsDMuqXGriDE2rXlOiBHS0lH
ICjAzCDE2rXltMIgNL/5IDEwwM+x7sH2uLggwK/Iv8fVtM+02Sk8L2ZvbnQ+
PGJyPg0KPGZvbnQgc2l6ZT00PsDMuqXGrjE8L2ZvbnQ+OiA8Zm9udCBjb2xv
cj1ncmVlbiBzaXplPTQ+wMy6pcauILHisKMgs7u/oSDAzLjhuK69usauuKYg
sbjA1MfPvcO0wiC60LKytMIgMjAwuLjF6yC537zbtOvH4MC7ILmrt+G3ziDH
2CC15biztM+02S4gwMy44biuvbrGriCxuLjFv80gud+827Trx+AgvK268b26
uKYgtb+9w7+hILSpuLEgvPYgwNa0wiDAzCCx4si4uKYgs/XEocH2ILi2vcOx
4iC52bb4tM+02S4owMy44biuvbrGriCxuMDUyMQsILDtsLTAxyC537zbILXJ
IMDMuOGzu7/ruLggurizu8HWvcO46SC1y7TPtNkuILz2vcWwxbrOILbHx9Eg
wPrI8bChIMDaw7zA+8C4t84gx9i15biuseIgtqe5rr+hILz2vcWwxbrOuKYg
x9LB2SC48LijvcO09bbztbUgwPzH9CCwxsGkx8+9xyDHyr/kvvi9wLTPtNku
IMDaw7wgwM7FzbPdILbzwM6w+iC43sDPvK259rimIMiuw+bHz7+pIMDMILjw
teewzcDMILChtMnH2MGzvcC0z7TZLikgvLrAzrvnwMzGri+8usDOv+vHsCDA
zLjhsPogutK5/cDMuOEox8e287nMteUgwMy44SC17rXuKcC6ILmrt+EgMjAw
uLjF6yC537zbtOvH4CDAzLqlxq6/oSDH2LTnwMwgvsggtcu0z7TZLjwvZm9u
dD48YnI+DQo8Zm9udCBzaXplPTQ+wMy6pcauMjwvZm9udD46IDxmb250IGNv
bG9yPWdyZWVuIHNpemU9ND7AzLqlxq4gseKwoyCzu7+hIMDMuOG4rr26xq64
piCxuMDUx8+9w7jpILnfvNux4ijH0bjewM+537zbseK0ySzAzLjhuK69usau
IMGkuK6x4rTJW8bEwM+60MfSseK0ySDG98fUXSy89r3FsMW6zsOzuK6x4rTJ
LLr8uKUgud+82yyx17iywLsgwMy/68fRIMDavLzH0SC1tb/yuLtbwMy44bi2
xMnGwyDDs8C9IL3DwNvHz73DtMIgutC1tSC757/rsKG0yV0ptbUgsLDAzCC1
5biztM+02S4gv6m3r7TrwMcgxMTHu8XNv6Egtb+9wyC757/rsKG0ycfVtM+0
2S48YnI+DQo8Zm9udCBjb2xvcj1yZWQ+ua7Ax8fPvccgtqcgwMy6pcauIMTa
teW4piC+y7fBwda8vL+pLiDAzLqlxq4gseKwo8DMIMH2s6q8rSDAzLjhuK69
usauuKYgsbi4xcfPvcOwxbOqIMDMuqXGriDE2rXluKYgwabD4sfPwfYguPgg
x8+9w7jpIMDMuqXGriDH/cXDwLsgud7AuL3HILz2IL74vcC0z7TZLjwvZm9u
dD48L2I+PC9mb250PjwvcD4NCg0KPHA+PGZvbnQgY29sb3I9Ymx1ZSBzaXpl
PTQ+PGI+wKcgPHU+NLChwfYgwMy44biuvbrGrjwvdT63ziCxuLy6tcggOTUw
MLi4sLMgwMy44biuvbrGrrimIDxmb250IGNvbG9yPXJlZD4xNbi4v/i/oTwv
Zm9udD4gxse4xcfVtM+02S4gwPy827y6sPggOLnpuLiwsyDAzLjhuK69usau
wMcgud+827f8wMwgNTAlwMzHz7fOILOqv8MgsOa/7CDIr7rSx9ggteW4rrDa
vcC0z7TZLjxicj48YnI+DQq6uLTZIMDavLzH0SCzu7/rsPogwda5rrnmuf3A
uyC+y7DtIL3NwLi9w7jpICA8YSBocmVmPSJtYWlsdG86a29yZWFydWxlc0Bu
YXZlci5jb20iPmtvcmVhcnVsZXNAbmF2ZXIuY29tPC9hPiDAuLfOILmuwMfH
2MHWvcO46SC1y7TPtNkuILmuwMe9wyC8usfUL7+stvTDs7imILOyseK9w7jp
ILChwOUgu6G4riDDs7iux9ggteW4rrDavcC0z7TZLiA8L2I+PC9mb250Pjwv
cD4NCg0KPHA+PGZvbnQgY29sb3I9cmVkIHNpemU9ND48Yj690bjAv6EgNbi4
v/jCpbiuIMDMuOG4rr26xq64piCxuMDUx8+9w7DtIL6yt7mx4sOzt7MgvrW4
8L74tNm0wiC7573Hv6Egs+62873FILrQtekguLnAuL3Hsq60z7TZLiCx17ex
IMDMuOG4rr26xq4gutnA4rDtIL3iyPfA2rTPIL7GsfWw7SC537zbx8/A2rTP
IMHXsKy02bDtILTAs6K9xyCyrrTPtNkuILHXt7EgutC16cC6IMD6yPHAxyDA
zLjhuK69usauuKYgsKHB9rDtILTZvcMgv/ix4rimIMi4urnHz73DseYgudm2
+LTPtNkuIMiruri0wiC75773wMcgv/i1v7fCwNS0z7TZLiDIq7q4wNrDvLim
IMb3seLH0iC8+CC++LTCIMDPwNS0z7TZLiC75773x8+9w7TCILTUteksIMit
wMzGwyEhPC9iPjwvZm9udD48L3A+DQoNCjxwPsDMILjewM/AuiDIuL3FwMwg
tcfB9iC+yr3AtM+02S4gvPa9xbDFus60wiA8YSBocmVmPSJtYWlsdG86a29y
ZWFydWxlc0BuYXZlci5jb20/c3ViamVjdD289r3FsMW6ziI+v6mx4jwvYT64
piDFrLivx9ggwda8vL/kLjwvcD4NCjxwPklmIHlvdSBwcmVmZXIgbm90IHRv
IHJlY2VpdmUgZnVydGhlciBlLW1haWxzIG9mIHRoaXMgdHlwZSBmcm9tIHVz
LCBwbGVhc2UgPGEgaHJlZj0ibWFpbHRvOmtvcmVhcnVsZXNAbmF2ZXIuY29t
P3N1YmplY3Q9UkVNT1ZFIj5DbGljayBoZXJlPC9hPjwvcD48YnI+PC90ZD48
L3RyPjwvdGFibGU+DQo8L2ZvbnQ+DQo8L2JvZHk+DQo8L2h0bWw+

------=_NextPart_15A_C372_4F43D4E8.AE26CBB9--

_______________________________________________
Trigtran mailing list
Trigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/trigtran



From mailnull@www1.ietf.org  Mon Apr  7 17:40:55 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06794
	for <trigtran-archive@odin.ietf.org>; Mon, 7 Apr 2003 17:40:55 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h37LjKn16170
	for trigtran-archive@odin.ietf.org; Mon, 7 Apr 2003 17:45:20 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37LjK816167
	for <trigtran-web-archive@optimus.ietf.org>; Mon, 7 Apr 2003 17:45:20 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06780
	for <trigtran-web-archive@ietf.org>; Mon, 7 Apr 2003 17:40:22 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37Lj8816147;
	Mon, 7 Apr 2003 17:45:08 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37Lic816113
	for <trigtran@optimus.ietf.org>; Mon, 7 Apr 2003 17:44:38 -0400
Received: from web10908.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA06758
	for <trigtran@ietf.org>; Mon, 7 Apr 2003 17:39:36 -0400 (EDT)
Message-ID: <20030407214208.77115.qmail@web10908.mail.yahoo.com>
Received: from [12.237.229.250] by web10908.mail.yahoo.com via HTTP; Mon, 07 Apr 2003 14:42:08 PDT
Date: Mon, 7 Apr 2003 14:42:08 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
To: minutes@ietf.org
Cc: trigtran@ietf.org, Carl Williams <carlw@mcsr-labs.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Trigtran] TRIGTRAN IETF 56 BoF Notes - revised for publication
Sender: trigtran-admin@ietf.org
Errors-To: trigtran-admin@ietf.org
X-BeenThere: trigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=unsubscribe>
List-Id: Triggers for Transport <trigtran.ietf.org>
List-Post: <mailto:trigtran@ietf.org>
List-Help: <mailto:trigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=subscribe>

Our revised minutes follow. Please let us know if you have any
questions or comments.

Spencer, for Spencer and Carl

------------------------------------

Triggers for Transport BOF (trigtran)

Thursday, March 20 at 0900-1130
===============================

CHAIRS:	Carl Williams <carlw@mcsr-labs.org>
	Spencer Dawkins <spencer_dawkins@yahoo.com>

Thanks to our minutes-takers:		
        Kevin Fall <kevin.fall@intel.com>	
	Tom Hiller <tomhiller@lucent.com>

Revisionism - Carl and Spencer were experimenting with the 
terms "connectivity interrupted" and "connectivity restored" in 
the framework draft and in the BoF, because "link down" 
and "link up" didn't map cleanly onto multi-hop subnetwork 
technologies, but we're going back to "link down" and "link up" 
as "clear enough" - and these terms will be used in the BoF 
minutes.

BoF Coordinates:

General Discussion: trigtran@ietf.org
To Subscribe: trigtran-request@ietf.org
In Body: subscribe
Archives:
www.ietf.org/mail-archive/working-groups/trigtran/current/maillist.html

BOF agenda and description:
http://www.ietf.org/ietf/03mar/trigtran.txt

Final Agenda:

- Introductions, Scribes, Jabber Scribes, Agenda-Bashing

- Status Update and Strawperson Statement of Work

- Issues identified in Framework draft

- Questions leading to a WG charter

- Next Steps to a TRIGTRAN working group?

Status Update and Strawperson Statement of Work
-----------------------------------------------

There are two current Internet-Drafts produced by Carl and 
Spencer as straw-person proposals on a problem statement and a 
framework. These drafts are

	draft-dawkins-trigtran-framework-00.txt
	draft-dawkins-trigtran-probstmt-01.txt

This BoF is a "second BoF". The first TRIGTRAN BoF was held at 
IETF 55, and focused on the problem statement; this BoF focused 
on what we learned from doing a framework proposal and on next 
steps to chartering TRIGTRAN as a working group.

Spencer made the canonical TRIGTRAN disclaimers:

- TRIGTRAN isn뭪 L2 triggers

- TRIGTRAN trigger delivery not guaranteed

- No notification ACKs; partial deployment scenarios

The framework draft considers 3 canonical triggers:

-	Link up
-	Link down 
-	Packet Discarded by subnetwork, not due to connection

"Link Up" seems easier in the short term.  There is some 
previous thinking on it: see Phil Karn뭩 posting on "Kicking 
TCP" on PILC list 3/2000m available at  
URL: http://pilc.lerc.nasa.gov/pilc/list/archive/0691.html

As for "Link Down", this notification "should" make sense. It 
does make sense intuitively. The problem is that the response 
might be application-specific - some TCP senders might wait 
longer to close a TCP connection, while others might give up 
sooner. Is there a canonical response? We need to understand 
the applications better before we can posit how to respond to 
this notification.

As for "Packet Discarded", we've realized that in a cellular 
environment this notification may result from a handoff - if 
so, the TCP sender would already have received a Link Up 
indication from the TCP receiver over its new connection path. 
Conceptually, a TCP sender should slow-start when path 
bandwidth changes, but if the mobile has merely moved from a 
lightly loaded cell to another lightly loaded cell, TCP could 
just continue in its current state without going to slow start. 
The new cell is as likely to be less congested as it is likely 
to be more congested, so ignoring the handoff, as TCPs do 
today, is still a reasonable strategy. Would telling the 
transport really help?

Spencer summarized a private conversation with Mark Allman 
as, "Gee, maybe TCP does pretty well often times on its own. 
You may be able to find cases where you could do better with 
notifications, but by the time you make sure the response to a 
notification doesn't have undesirable side effects in other 
cases, TCP doesn't look so bad"

Co-chair summary Link Up seems ready for prime-time, Link Down 
may be in the near future; Packet Discarded seems less ready.

Spencer (and Carl) proposed a strawperson Statement of Work:

- spin up working group and do 멿ink up�
	Specify response for dup pkts during RTO
	Safe, good consensus

- investigate 멿ink down� semantics
	What should transport do here?  

- investigate explicit mechanisms
	Can we send OOB signals in the Internet in 2005?

- build consensus on wish list for IAB/IRTF investigation?
	Horizontal handoff, non-congestion loss, corruption
	Send wish list to Leslie and Vern and ask for help
        (this is something mobileIP and others are doing)

-- Q and A --

Sally Floyd: terminology: why 밹onnectivity restored� vs "link 
up"? One link up might not have anything to do w/e2e 
connectivity

Spencer: You뭨e right � the previous 멿ink up� term is more 
appropriate

Bernard Aboba: need to be clear about the meaning of 
notifications. There's a distinction between link 몍p� 
vs 멹ully functional� - a link can be 뱔p� but may not provide 
very useful connectivity. It can be quite tricky as to  just 
when you send the trigger.

Spencer: Would notifications about nominal BW changes be useful?

Bernard: I was just thinking re link up; but if I was told of a 
rate change that doesn뭪 seem so obviously relevant

Kevin Fall: you may have cases in which the link is 몍p� but 
error rate is rather too bad to be very useful.  This has been 
explored some time ago in SCPS.

Phillipe Gentric: knowing a rate change could be quite helpful 
for streaming media

Spencer: Maybe a bandwidth change would be some form of maximum 
[a speed limit through a link], so the indicator is essentially 
saying you might as well not go faster than that to the 
transport.

Allison Mankin: maybe we are out of scope here; we don뭪 really 
have links that tell us their max bandwidth at the moment

Sally: It's not obvious what scope should be; some things have 
been investigated but others haven뭪 been.  At a minimum, maybe 
TRIGTRAN could write a problem statement. This group could 
define the trigger; sending the entire problem to a research 
group may not be enough, but a problem statement might well be 
appropriate.  

Eg. DCCP partial checksum issue came up.  Should you allow 
corrupted data to be delivered to apps [or to lower layers].  
Or should it be marked somehow as corrupted.  Where would this 
sort of issue be addressed? perhaps here, or perhaps somewhere 
in IRTF.  

Another: as we build transport protocols robust to re-ordering, 
[and there is no reason they couldn뭪 be]--- would you want a 
way for the transport to tell some lower layer that it robust 
to re-ordering so feel free to re-order.  So, I don뭪 know.  
Not clear where speculative, fleshing-out activities should 
take place.

Spencer: We have been trying to maximize the amount of sanity 
we appear to have.  We were trying to stay grounded in minimal 
notifications, not to spend time thinking about what to 
usefully speculate about. Now that we've been through a 
strawperson framework, maybe it would make sense now to add 
some of these speculative things to the discussion topics.

Mark Handley: Various forms of these issues have arisen over 
the years.  We don뭪 have good institutional memory.  If we 
investigate why *not* to do something, we should write this 
down somewhere, so we can remember why we *don't* do things.

Spencer: Yes, I found some things like this looking over older 
discussions.

Allison Mankin: We have a group of community members in the 
IETF who are largely not researchers; there are some 
interesting questions (e.g. how long to wait, what to do, is it 
really up or down, etc).  Just getting this right is useful � 
there is engineering to do with issues like "link flapping".  
We aren뭪 inventing a research group here.  I뭢 trying to not 
sound too 몋op down� here.  We would not want to include the 
researchy stuff in the charter.  Probably having a wish list 
possibly for another group might be good, but we should not be 
doing work such as congestion handling here.

Bernard: The more I learn, the more I would like to have a 
document that describes the general characteristics of various 
links.  A link tutorial for the group would be useful.  Of the 
existing literature, what are the results and conclusions?  
These are not static characteristics but dynamic ones.  I take 
this to mean a survey document.  This would be the first item 
of order to complete. It's not exactly the same stuff that PILC 
did.  Maybe different than PILC because here we are concerned 
with signaling, which is more dynamic.

Allison: You are suggesting a sort of survey doc?  That would 
be part of the charter[?] hmmm.

Spencer: TCP-SAT WG produced a doc that summarized the research 
topics.

Allison: yeah, maybe ok.  We would like to have a well and 
narrowly focused group.  This is my answer to Sally.  Now we 
have Bernard's suggestion.

Spencer: Maybe we could do this in parallel [both the research 
and engineering-ish documents]

Aaron Falk: [former chair of TCP-SAT] I뭢 not sure that the 
research doc was so useful.  I wouldn뭪 be opposed to seeing it 
again, but wouldn뭪 want to take WG resources away from other 
tasks.  There are all sorts of subtleties.  The charter must be 
narrow and well focused. I would rather go deep than broad.  I 
don뭪 see that a TRIGTRAN research mechanisms document is a 
great investment of resources.

Gorry Fairhurst: there are many things we could signal, but we 
don뭪 know what we would do.  I think doing a big survey would 
unearth lots of stuff we probably don뭪 want to deal with.

Spencer: Doing the framework revealed a fairly rich set of 
things that come up.

Bernard: Given a media, how reliable is an indication?  This 
sort of documentation could be quite useful.  So, a [control] 
system observing an indication has to have some understanding 
of what to believe.  This applies to rates also.  The question 
is how reliable is it, how much skepticism should be applied 
when receiving a trigger.

Spencer: Carl and I were assuming it would be helpful to know 
what different subnet technologies had the capability to send.  
Bernard is perhaps stating that the mapping of link condition 
to trigger could be more formal than we had been thinking.  
Hmmm.

Allison: Maybe an appendix could include examples that could be 
cautionary or provide examples.  Gathering those would be good. 
The working group could contribute these.

Vince Park: I agree w/Bernard.  It is difficult to decide what 
to take as an indication and how to interpret it.  Probably a 
good idea.  Has come up in mobileIP, MANET, and others.  
Ultimately you have to decide how to map L2 type information 
into a higher-layer indicator. May be bigger scope than TSV-
only.

Ethan Blanton: for some triggers we aren뭪 sure we need a 
*protocol*.  Not sure it is worth putting that much energy into 
a protocol until we are sure we need one.

Aaron Falk: We're not just talking about the format of "bits on 
the wire". We need to define the semantics of what 
notifications you get and how you respond.  None of that stuff 
has been hashed out.  I believe some of these things may be 
valuable, but maybe there are cases where there are problems.  
There is work to do there.

Ethan: I didn뭪 mean to indicate that we shouldn뭪 do this 
work.  Just maybe a first-order item may be not to define the 
protocol, but whether or not a small subset of triggers are 
needed given certain links.

Spencer: I would like to agree.  The mechanism appropriate for 
link up is different from every other notification we뭭e talked 
about.  If all we have to do is link up, we don뭪 need the 
whole framework.  Is this responsive to your question?

Ethan: yeah, I think so.  If you carve out a space that doesn뭪 
need a protocol, you could still be concerned with what to do.

Rick: from Mobile IP, we have been playing w/L2 triggers.  
Getting their semantics sorted out is important.  We may need 
them for all sorts of things.

Mark Allman: I뭢 not so concerned about 멿ink up� per-se, but 
exactly what you should do with it should be taken with some 
caution.   (e.g. DCCP with this indication would do what 
exactly?)

Spencer: We뭭e been encouraged to look at other transports 
(e.g. SCTP).  Now that DCCP seems to exist, we should be 
looking there too.

Sally: I agree the question is open as to implicit vs explicit 
signals and that we need definitions for explicit ones and 
descriptions for implicit ones.  Explicit signals might not be 
the right answer.

Mark Handley: Does the sender of the signal need to know about 
all future transports?  This is a complex space뾦nteractions 
with lots of things [tunnels, security whatever].  Need to be 
careful.

Spencer: My experience is that transport area is cautious.

Randall Stewart: I also don뭪 know what I would do on link-up 
in SCTP stack.  Other than (some) relationship to heartbeats, 
I뭢 not sure how useful this is.

Spencer: I had thought TCP people want link up and SCTP people 
want link down, based on conversations at IETF 55.

Randall: I feel somewhat uncomfortable with link down given the 
possible DoS issues.

--- Issues in the framework draft�

Aaron Falk suggested that we focus this discussion on Link Up, 
because we haven't gotten consensus on another notification 
that's compelling

Spencer: link-up needs very little framework, and other stuff 
isn뭪 baked yet. The framework document is not really a 
completed framework.  We are exploring an approach.

Aaron: Spencer, I뭗 like to suggest that we might have a 
consensus in the room that there is strong support for link-up 
and maybe some opposition to others.  If you accept that, the 
framework is somewhat superfluous in the context of just doing 
link-up.  Take a poll of the room to see.

--- Agenda and WG charter and scope issue ---

Spencer: I appreciate your suggestion re going forward on link-
up.

Aaron: What might be an acceptable scope of work for this WG is 
the question.

Spencer: How about link-up?  Is there is consensus that working 
on link-up would be just fine?

*** Room Consensus was that Link Up is just fine ***

Aaron: Does anyone this think would be a *bad* idea?

Spencer: Yes, and please tell us why?

Spencer: If we charter as a WG, I'm looking at whether this 
would be in scope.

Joe Zebarth: It appears to be premature if this will move 
beyond a BOF.

Spencer: What questions remain to be answered?

Joe: Are you proposing a new protocol or mod to existing one?  
If I뭢 sending UDP say do I get one of these triggers?  Are we 
modifying TCP or doing a new protocol or what?  We need more 
info to agree or disagree for a WG formation.

William Ivancic: There are unanswered questions regarding the 
usefulness of link-up. This isn't IETF-ready yet.

Spencer: The criteria for having an item in the WG charter is 
not that we already know the answer, but that we are pretty 
sure we could come up with one.

Dick Knight: I뭢 still confused.  What is the clear problem 
statement?  Most of this link layer stuff will sort itself 
out.  I뭢 not sure why you are working this problem.  Is this 
going to work in an MPLS network?

Reiner Ludwig: To those people who said 몁o�, people aren뭪 
convinced we have a problem.  Various people don뭪 know what to 
do with it.  I don뭪 think people in this room are convinced 
there is a problem.

Aaron: I think part of the problem is that not all these people 
have been at the places where this has come up before and that 
the drafts don뭪 fully capture these experiences.  E.g. the 
reference to Phil Karn뭩 stuff in PILC.  The people here that 
are familiar with the PILC document are not the ones that have 
objected [except Reiner]. Responding to Reiner in particular, 
there are some questions regarding SCTP, DCCP, and TFRC.  One 
way to go is to take the suggestion from the PILC doc that you 
re-transmit packets at the routers [which doesn뭪 require 
changes in end stations].  Part of the problem here is not 
everybody understands all the issues.  We may need to talk 
about this뾲here isn뭪 a consistent sense as to what is on the 
table.  2 pieces of the problem:  should IETF be trying to 
solve this, should the IETF try to solve this and what is the 
form of the solution so people can see it is not dangerous.

Spencer: I do have a couple of slides here to present that 
might help.  Phil Karn뭩 proposal is best described in a 
posting on the PILC list from 3/2000.

Mark Handley: Trying to summarize.  A general strategy used in 
many of our transport protocols is exponential backoff.  You 
would like to not have to wait for exponential backoff if you 
know the link has actually failed.

Spencer: So, like in TCP, this could be quite some time [to 
wait].

Bernard: I think there is some problem getting the timer to the 
right point.  Eg. There can be rate changes between media [e.g. 
between 802.11 and GPRS].  Question is how long it takes to 
adjust.  Also, sometimes the adjustment can be 2-3 orders of 
magnitude.  The first thing you need is a well-defined problem; 
next is what does the literature say?  Does this literature 
solve the problem, or is something else needed?  If you go 
through this logically, then get to the end and figure out 
whether you have solved it [or not].  Then you have a logical 
problem statement and you figure out what is left.  (e.g. if 
the receiver changes rate dramatically, does or how does the 
sender know)?

Spencer: First thing I뭢 going to show you now is generally 
about the framework; next is more specific to TCP {뱆icking� 
TCP}.  Kicking TCP doesn뭪 appear to be so difficult, but I뭢 
afraid if we go beyond this we need much more organizational 
machinery.

Mark Handley: please don뭪 talk only about TCP; the exponential 
backoff is ubiquitous for other transports too.

{Explanation of slides � lots of details here, see the slides, 
in particular the one titled "If we really 멾ick TCP". Phil 
Karn, 밙icking TCP� March 2000 PILC list posting reference 
appears at the top of these minutes}

Sally Floyd: I would feel more comfortable with a problem 
statement before the framework.  Basically what Bernard has 
suggested.  I would feel much more grounded to start there.

Spencer: I agree completely.  We did some problem stmt work up 
front; it would be appropriate to continue from there.

Bernard: these indications have effects on things other than 
TCP.  For example, maybe I need to update my address lease.  
So, that would certainly change things if I lost my address!

Allison: This is the third in a series of BOFs that seems to be 
trying to not generalize the overall triggers problem.  Is this 
part of the Internet area; seems that it isn뭪 happening there 
either.  Nobody seems to want to own it.  I have a general 
question � I should ask 밾ow pressing is this problem�?  How 
often do we get caught in this state?  Maybe this inconvenience 
isn뭪 worth the effort [like building the WG].  Maybe we should 
take a poll as to whether you have this problem?

Spencer and Carl: Hand poll was maybe 30 people or so that felt 
they had this problem.

Reiner: I'm looking at TCP over wide-area wireless networks 
(cellular 2.5G/3G, mostly GPRS and WCDMA; not SAT though) for 
a couple of years now, and I know of many real world
measurements, not all of which have been made public. But, 
the problem of a TCP sender that is stuck with a backed-off 
RTO due to some transient link outage is rare in these 
environments. It does happen occasionally, though.

Bernard: it isn뭪 a big problem on 802.11, and again you have 
to be really careful about how you treat the indications [what 
sort of filter you use]

Allison: so we might say don뭪 do this for 802.11.  Now I think 
we take a charter proposal, unless there is some objections?

Alex Audu: is there an option to do both link up and down? 

Spencer: Well, no, not yet

Alex: Are we going to ask this question?

Carl: Does anything other than link-up make sense for a charter?

Kevin: there is an observation that these indications can 
affect other layers of the stack.  If we charter narrowly, 
where will this be addressed?

Tom Hiller:  there is some advantage to link down in 3GPP

Spencer: We have been assuming these indications are pretty 
much un-authenticated.  So therefore what they can indicate is 
limited.  So we have been living under this constraint.

William: but can뭪 I have similar issues with link up?

Spencer: I wasn뭪 so concerned with getting a link up than a 
link down.  It doesn뭪 seem as risky as link-up - the network 
effect of link up is the same as an RTO timer popping.

Mark Allman: it's all in how you scope the response to an 
indication.  Link-up could be dangerous if you blast.  Not if 
you are conservative, I would think.

Spencer: Comments on sending some of this to the IRTF?

Kevin: Who covers things covering various layers?  Is it 
possibly IRTF?

Aaron: Kevin, maybe this could be a result of just doing it.  
The process can be adapted.  I뭢 an advocate of being closed 
and well defined.  I뭢 increasingly unhappy with how long the 
turn around time is on documents.

Spencer: Is it worth talking about 뱊on-engineering� things 
here?

Sally: It seems like there are architectural issues here.  
Having an IRTF home for this seems perfectly plausible to me.  
Whether it is an IRTF group or just a bunch of people doesn뭪 
seem so important.

Spencer: What we are talking about is can we discuss things 
that might be outside the WG?

?? � I know we뭭e talked about link up and link down.  What, in 
total, are we talking about?

Spencer: In my complete list, including researchy topics, I had 
described link up, link down, packet discard, possibly 
horizontal or vertical handoff, and maybe indication of 
corruption losses

Sally: I think a group of people writing about particulars 
could also write about more arch/speculative things too

Gorry: We touched on timescales; we뭭e moved to link up/down, 
ok.  There is a semantic gap to what the link understands and 
what we are looking for.  But we need to understand the 
filtering better.  There is work to do that is technology 
dependent.

Allison: This WG is not going to spend lots of cycles trying to 
have architectural discussions.  It is going to spend its time 
working on the work.

Spencer: yes

Allison: It's going to do the work, right?  Don뭪 spend too 
much time carefully placing the work [that we don뭪 intend to 
do here] somewhere else. 

Spencer: Allison, can we go forward?

Allison: I뭢 going to wait for a charter proposal from you.  It 
should include milestones, etc.  I think we have gone as far as 
we can go so far.  No further progress can be made without the 
proposal.  My sense of the room is that the work is compelling. 
I don뭪 need any more info. That was the last question I needed 
to answer to proceed.

Spencer: Are we going the right direction toward a charter?

Allison: You need to say this is a real-world problem.  Scope 
the work carefully.  Charters are contracts.  Want to make sure 
the folks here are committed to doing engineering work on the 
problem.  Mark Handley reminded me that in the PILC Advice to 
Internet Subnetwork Designers (LINK) Internet-Draft there is 
(almost) a BCP how routers might use link indications to hold 
packets when links go down.  Be careful about security 
considerations and scope.  There has been a lot of chatter in 
small groups regarding lightweight semi-secure mechanisms for 
protection w/out full crypto.  Then we show a WG charter 
proposal to IAB/IESG, chairs participate in this discussion, 
then to the full IETF.  Then we have consensus of everybody, 
then we have a contract.  Then we hold to it very closely.  By 
then it has IAB review and IESG approval and is advertised to 
others.  This then might involve liaison with other standards 
bodies (IEEE in this case seems interested).

Spencer, after closing remarks:  Has anyone looked at the 
purpose built keys (PBK) draft?

_______________________________________________
Trigtran mailing list
Trigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/trigtran



From mailnull@www1.ietf.org  Mon Apr  7 17:48:41 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06932
	for <trigtran-archive@odin.ietf.org>; Mon, 7 Apr 2003 17:48:41 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h37Lr6Y16439
	for trigtran-archive@odin.ietf.org; Mon, 7 Apr 2003 17:53:06 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37Lr6816436
	for <trigtran-web-archive@optimus.ietf.org>; Mon, 7 Apr 2003 17:53:06 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06915
	for <trigtran-web-archive@ietf.org>; Mon, 7 Apr 2003 17:48:10 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37Lr1816427;
	Mon, 7 Apr 2003 17:53:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h37LqK816404
	for <trigtran@optimus.ietf.org>; Mon, 7 Apr 2003 17:52:20 -0400
Received: from web10902.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA06898
	for <trigtran@ietf.org>; Mon, 7 Apr 2003 17:47:23 -0400 (EDT)
Message-ID: <20030407214956.18602.qmail@web10902.mail.yahoo.com>
Received: from [12.237.229.250] by web10902.mail.yahoo.com via HTTP; Mon, 07 Apr 2003 14:49:56 PDT
Date: Mon, 7 Apr 2003 14:49:56 -0700 (PDT)
From: Spencer Dawkins <spencer_dawkins@yahoo.com>
To: trigtran@ietf.org
Cc: Carl Williams <carlw@mcsr-labs.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1167160974-1049752196=:18017"
Subject: [Trigtran] Proposed TRIGTRAN Charter - pre-IESG version
Sender: trigtran-admin@ietf.org
Errors-To: trigtran-admin@ietf.org
X-BeenThere: trigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=unsubscribe>
List-Id: Triggers for Transport <trigtran.ietf.org>
List-Post: <mailto:trigtran@ietf.org>
List-Help: <mailto:trigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=subscribe>

--0-1167160974-1049752196=:18017
Content-Type: text/plain; charset=us-ascii
Content-Id: 
Content-Disposition: inline

Carl and I have submitted the following draft charter to
Allison, and wanted to let the mailing list know this (as a
status report).

The draft charter isn't completely roughed out - the version we
submitted to Allison has a couple of questions for her as well.

Allison will be working out the final charter as a contract with
a working group, so please be thinking of anything you see that
needs to be addressed in the charter.

Think narrowly defined, short-term deliverables, and achievable.

Thanks!

Spencer, for Spencer and Carl


--0-1167160974-1049752196=:18017
Content-Type: text/plain; name="TRIGTRAN Proposed Charter (SD 030402).txt"
Content-Description: TRIGTRAN Proposed Charter (SD 030402).txt
Content-Disposition: inline; filename="TRIGTRAN Proposed Charter (SD 030402).txt"

Triggers for Transports (trigtran) 

Chair(s):
Spencer Dawkins <spencer_dawkins@yahoo.com>
Carl Williams <carlw@mcsr-labs.org>

Transport Area Advisor:
Allison Mankin <mankin@psg.com>

Technical Advisor(s):
-------------- Allison, would an INT AD be useful here? We had one in PILC ---------------
-------------- and probably need one in TRIGTRAN more --------------------------------------

General Discussion: trigtran@ietf.org
To Subscribe: trigtran-request@ietf.org
In Body: subscribe
Archives: www.ietf.org/mail-archive/working-groups/trigtran/current/maillist.html

Description of Working Group:

The primary purpose of the TRIGTRAN Working Group will be the specification of explicit 
mechanisms used to notify transport implementations about subnetwork events.

The Performance Implications of Link Characteristics (PILC) working group has produced 
Best Current Practice specifications for TCP operation over 밹hallenged� subnetworks, 
without specifying changes to transport protocols. TRIGTRAN addresses many of the same 
뱎roblematic subnetworks� that PILC addressed, but TRIGTRAN may propose changes to 
transport protocols in order to support these subnetworks effectively.

BoF consensus at IETF 56 was that a 밚ink Up� notification could be provided safely, 
using end-to-end implicit messaging, and would be valuable in a number of environments. 
TRIGTRAN will focus first on 밚ink Up� as its prototype notification, because all other 
notifications will be more complex and require more framework than 밚ink Up� does.

TRIGTRAN specifications will address these points:

- The justification for a specific notification
- A choice between explicit and implicit notifications
- A choice between end-to-end and edge-to-end notifications
- A description of the notification itself
- A suggested transport response to this notification
- Implementation considerations for well-known subnetwork technologies
- Security considerations for this notification

The barrier for approval of a notification is tightly coupled with its security considerations. 
If light-weight 뱒emi-secure� mechanisms like 뱎urpose-built keys� are available and appropriate, 
a more aggressive response to a notification may be appropriate than a reasonable response to a 
completely-unauthenticated datagram notification arriving from anywhere in the connected Internet.

Relationship between TRIGTRAN and other IETF entities:

1. The PILC working group will suspend operation when the 밃dvice for Internet Subnetwork Designers� 
   draft is approved by IESG for publication.
2. -------------- Allison, how should TRIGTRAN interact with TSVWG? --------------- 
3. SCTP, DCCP, and other 뱊on-TCP� transport working groups

Goals and Milestones:
Aug 2003	Problem statement for 밚ink Up� notifications to IESG (Informational)
Aug 2003	Summary of possible notifications to IESG (Informational)
Dec 2003	Specification for 밚ink Up� to IESG {Experimental/Proposed Standard}
Dec 2003	Problem statements for other notifications to IESG, if required
Dec 2003	Recharter for other notifications or shutdown the working group


--0-1167160974-1049752196=:18017--
_______________________________________________
Trigtran mailing list
Trigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/trigtran



From mailnull@www1.ietf.org  Sat Apr 19 21:01:08 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13203
	for <trigtran-archive@odin.ietf.org>; Sat, 19 Apr 2003 21:01:08 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3K1BR516385
	for trigtran-archive@odin.ietf.org; Sat, 19 Apr 2003 21:11:27 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3K1BR816382
	for <trigtran-web-archive@optimus.ietf.org>; Sat, 19 Apr 2003 21:11:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13186
	for <trigtran-web-archive@ietf.org>; Sat, 19 Apr 2003 21:00:37 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1973ET-0000I8-00
	for trigtran-web-archive@ietf.org; Sat, 19 Apr 2003 21:03:01 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1973ES-0000I4-00
	for trigtran-web-archive@ietf.org; Sat, 19 Apr 2003 21:03:00 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3K1BF816360;
	Sat, 19 Apr 2003 21:11:16 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3K18Z816287
	for <trigtran@optimus.ietf.org>; Sat, 19 Apr 2003 21:08:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13133
	for <trigtran@ietf.org>; Sat, 19 Apr 2003 20:57:46 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1973Bi-0000HW-00
	for trigtran@ietf.org; Sat, 19 Apr 2003 21:00:10 -0400
Received: from [220.81.202.222] (helo=jnana)
	by ietf-mx with smtp (Exim 4.12)
	id 1973BZ-0000HE-00
	for trigtran@ietf.org; Sat, 19 Apr 2003 21:00:02 -0400
From: 카드해결박사<test@test.com>
To: trigtran@ietf.org
Date: Sun, 20 Apr 2003 09:59:37 +0900
Mime-Version: 1.0
Content-Type: text/html; charset="euc-kr"
Message-Id: <E1973BZ-0000HE-00@ietf-mx>
Subject: [Trigtran] (광고)어차피 인생한방이잖아! 그래도...
Sender: trigtran-admin@ietf.org
Errors-To: trigtran-admin@ietf.org
X-BeenThere: trigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=unsubscribe>
List-Id: Triggers for Transport <trigtran.ietf.org>
List-Post: <mailto:trigtran@ietf.org>
List-Help: <mailto:trigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h3K1BF816360
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>(=B1=A4=B0=ED)=BE=EE=C2=F7=C7=C7 =C0=CE=BB=FD=C7=D1=B9=E6=C0=CC=C0=
=DD=BE=C6! =B1=D7=B7=A1=B5=B5...</TITLE>

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Deuc-kr"=
>
</HEAD>
<BODY BGCOLOR=3D#FFFFFF LEFTMARGIN=3D0 TOPMARGIN=3D0 MARGINWIDTH=3D0 MARG=
INHEIGHT=3D0>
<table width=3D"102%" height=3D"100%" border=3D"0" cellpadding=3D"0" cell=
spacing=3D"0">
  <tr>
    <td align=3D"center" valign=3D"middle"><TABLE WIDTH=3D583 BORDER=3D0 =
CELLPADDING=3D0 CELLSPACING=3D0>
        <TR>=20
          <TD> <a href=3D"http://www.card-cash.co.kr/" target=3D"_blank">=
<IMG SRC=3D"http://www.card-cash.co.kr/MAIL-spam/mail-2/img/mail-2_01.jpg=
" ALT=3D"" WIDTH=3D220 HEIGHT=3D61 border=3D"0"></a></TD>
          <TD valign=3D"top"><table width=3D"100%" height=3D"1" border=3D=
"0" cellpadding=3D"0" cellspacing=3D"0" bgcolor=3D"#000000">
              <tr>
                <td></td>
              </tr>
            </table></TD>
          <TD> <a href=3D"http://www.card-cash.co.kr/" target=3D"_blank">=
<IMG SRC=3D"http://www.card-cash.co.kr/MAIL-spam/mail-2/img/mail-2_03.jpg=
" ALT=3D"" WIDTH=3D193 HEIGHT=3D61 border=3D"0"></a></TD>
        </TR>
        <TR>=20
          <TD> <a href=3D"http://www.card-cash.co.kr/" target=3D"_blank">=
<IMG SRC=3D"http://www.card-cash.co.kr/MAIL-spam/mail-2/img/mail-2_04.jpg=
" ALT=3D"" WIDTH=3D220 HEIGHT=3D109 border=3D"0"></a></TD>
          <TD> <a href=3D"http://www.card-cash.co.kr/" target=3D"_blank">=
<IMG SRC=3D"http://www.card-cash.co.kr/MAIL-spam/mail-2/img/mail-2_05.jpg=
" ALT=3D"" WIDTH=3D170 HEIGHT=3D109 border=3D"0"></a></TD>
          <TD> <a href=3D"http://www.card-cash.co.kr/" target=3D"_blank">=
<IMG SRC=3D"http://www.card-cash.co.kr/MAIL-spam/mail-2/img/mail-2_06.jpg=
" ALT=3D"" WIDTH=3D193 HEIGHT=3D109 border=3D"0"></a></TD>
        </TR>
        <TR>=20
          <TD> <a href=3D"http://www.card-cash.co.kr/" target=3D"_blank">=
<IMG SRC=3D"http://www.card-cash.co.kr/MAIL-spam/mail-2/img/mail-2_07.jpg=
" ALT=3D"" WIDTH=3D220 HEIGHT=3D170 border=3D"0"></a></TD>
          <TD> <a href=3D"http://www.card-cash.co.kr/" target=3D"_blank">=
<IMG SRC=3D"http://www.card-cash.co.kr/MAIL-spam/mail-2/img/mail-2_08.jpg=
" ALT=3D"" WIDTH=3D170 HEIGHT=3D170 border=3D"0"></a></TD>
          <TD> <a href=3D"http://www.card-cash.co.kr/" target=3D"_blank">=
<IMG SRC=3D"http://www.card-cash.co.kr/MAIL-spam/mail-2/img/mail-2_09.jpg=
" ALT=3D"" WIDTH=3D193 HEIGHT=3D170 border=3D"0"></a></TD>
        </TR>
        <TR>=20
          <TD> <a href=3D"http://www.card-cash.co.kr/" target=3D"_blank">=
<IMG SRC=3D"http://www.card-cash.co.kr/MAIL-spam/mail-2/img/mail-2_10.jpg=
" ALT=3D"" WIDTH=3D220 HEIGHT=3D94 border=3D"0"></a></TD>
          <TD> <a href=3D"http://www.card-cash.co.kr/" target=3D"_blank">=
<IMG SRC=3D"http://www.card-cash.co.kr/MAIL-spam/mail-2/img/mail-2_11.jpg=
" ALT=3D"" WIDTH=3D170 HEIGHT=3D94 border=3D"0"></a></TD>
          <TD> <a href=3D"http://www.card-cash.co.kr/" target=3D"_blank">=
<IMG SRC=3D"http://www.card-cash.co.kr/MAIL-spam/mail-2/img/mail-2_12.jpg=
" ALT=3D"" WIDTH=3D193 HEIGHT=3D94 border=3D"0"></a></TD>
        </TR>
        <TR>=20
          <TD height=3D"200" colspan=3D"3">
<table width=3D"583" height=3D"200" border=3D"0" cellpadding=3D"0" cellsp=
acing=3D"1" bgcolor=3D"#000000">
              <tr>=20
                <td align=3D"center" bgcolor=3D"#D1D1D1"> <table width=3D=
"580" border=3D"0" cellspacing=3D"0" cellpadding=3D"5">
                    <tr bgcolor=3D"#EAEAEA">=20
                      <td height=3D"47" align=3Dcenter bgcolor=3D"#EAEAEA=
"> <div align=3D"center"><font color=3D"#333333" size=3D"2">=B1=CD=C7=CF=C0=
=C7=20
                          =BD=C2=B6=F4=BE=F8=C0=CC =C8=AB=BA=B8=BC=BA =C0=
=FC=C0=DA =BF=EC=C6=ED=C0=BB =BA=B8=B3=BB=B0=D4 =B5=C8 =C1=A1 =C1=A4=C1=DF=
=C8=F7 =BB=E7=B0=FA =B5=E5=B8=B3=B4=CF=B4=D9. <br>
                          =C1=A4=BA=B8=C5=EB=BD=C5=B8=C1=C0=CC=BF=EB =C3=CB=
=C1=F8=B9=FD =B1=D4=C1=A4=C0=BB =C1=D8=BC=F6=C7=CF=BF=A9 <span class=3D"f=
1">(=B1=A4=B0=ED)=B8=DE=C0=CF=C0=D3</span>=C0=BB=20
                          =C7=A5=BD=C3=C7=CF=BF=B4=C0=B8=B8=E7, <span cla=
ss=3D"f1"><br>
                          =BC=F6=BD=C5=B0=C5=BA=CE =C0=E5=C4=A1=B8=A6 =B8=
=B6=B7=C3</span>=C7=CF=B0=ED =C0=D6=BD=C0=B4=CF=B4=D9.<br>
                          =B1=CD=C7=CF=C0=C7 =C0=FC=C0=DA =BF=EC=C6=ED =C1=
=D6=BC=D2=B4=C2 www1.ietf.org/mail-archive/working-groups/pilc/current/ms=
g00233.html=BF=A1=BC=AD 2003-04-20 =BF=C0=C0=FC 12:17:01=BF=A1 =BD=C0=B5=E6=
=C7=CF=BF=B4=C0=B8=B8=E7, <br>
                          =C0=FA=C8=F1=B4=C2 =B1=CD=C7=CF=C0=C7 =C0=FC=C0=
=DA=BF=EC=C6=ED =C1=D6=BC=D2 <br>
                          =BF=DC =BE=EE=B6=B0=C7=D1 =B0=B3=C0=CE=C1=A4=BA=
=B8=B5=B5 =B0=A1=C1=F6=B0=ED =C0=D6=C1=F6 =BE=CA=C0=B8=B9=C7=B7=CE =BE=C8=
=BD=C9=C7=CF=BD=C3=B1=E2 =B9=D9=B6=F8=B4=CF=B4=D9. =BC=F6=BD=C5=C0=BB =BF=
=F8=C4=A1 =BE=CA=C0=B8=BD=C3=B8=E9 =BE=C6=B7=A1=C0=C7=20
                          <br>
                          <b>=B8=DE=C0=CF=BC=F6=BD=C5=B0=C5=BA=CE</b>=B8=A6=
 =C5=AC=B8=AF=C7=D8 =B1=CD=C7=CF=C0=C7 =C0=CC=B8=DE=C0=CF=C0=BB =C0=FC=BC=
=DB=C7=CF=BF=A9 =C1=D6=BD=C3=B0=C5=B3=AA '=BC=F6=BD=C5=B0=C5=BA=CE'=B6=F3=
=B4=C2 =C1=A6=B8=F1=C0=B8=B7=CE=20
                          =BE=C6=B7=A1=C0=C7 =B8=DE=C0=CF(<b>kdj5823@nave=
r.com</b>)=B7=CE =B4=E4=C0=E5=C1=D6=BD=CA=BD=C3=BF=C0. =C1=EF=BD=C3!! =BB=
=E8=C1=A6=C7=CF=BF=A9=20
                          =B4=D9=BD=C3=B4=C2 =B8=DE=C0=CF=C0=BB =BA=B8=B3=
=BB=C1=F6 =BE=CA=B0=DA=BD=C0=B4=CF=B4=D9. <br>
                          =B2=C0 =C1=A6=B8=F1=BF=A1 '<b>=BC=F6=BD=C5=B0=C5=
=BA=CE</b>' =B9=AE=C0=DA=B0=A1 =B5=E9=BE=EE=B0=A1=BE=DF =C7=D5=B4=CF=B4=D9=
.</font><font size=3D"2"><br>
                          </font></div></td>
                    </tr>
                  </table>
                  <table width=3D"580" border=3D"0" cellspacing=3D"0" cel=
lpadding=3D"0">
                    <tr>=20
                      <td height=3D"25"> <div align=3D"center"><a href=3D=
"http://www.redbrush.co.kr/email/reject.jsp?keyword=3Dcardcash&email=3D%5=
B%5BEMAIL%5D%5D&type=3Dreject" OnMouseOver=3D"window.status=3D''" OnMouse=
Out=3D"window.status=3D''"><img src=3D"http://www.card-cash.co.kr/MAIL-sp=
am/img/btn02.gif" width=3D"70" height=3D"20" border=3D"0"></a></div>
                        <div align=3D"center"> </div></td>
                    </tr>
                  </table>
                  <table width=3D"580" border=3D"0" cellspacing=3D"0" cel=
lpadding=3D"0">
                    <tr>=20
                      <td> <div align=3D"center"><a href=3D"mailto:kdj582=
3@naver.com" class=3D"link"><font size=3D"2"><b><font color=3D"#336699">=C0=
=A7=C0=C7=20
                          =BC=F6=BD=C5=B0=C5=BA=CE =B1=E2=B4=C9 =BA=D2=B4=
=C9=BD=C3 =BC=F6=BD=C5=B0=C5=BA=CE =B8=DE=C0=CF<br>
                          My Reply E-mail. Click!! : kdj5823@naver.com</f=
ont></b></font></a>=20
                        </div></td>
                    </tr>
                  </table>
                  <table width=3D"580" border=3D"0" cellspacing=3D"0" cel=
lpadding=3D"5">
                    <tr bgcolor=3D"#EAEAEA">=20
                      <td height=3D"47" align=3Dcenter bgcolor=3D"#EAEAEA=
"> <div align=3D"center"><font color=3D"green" size=3D"2"><font color=3D"=
0368A9">We=20
                          inform you, inaccordance with the advise of Min=
istry=20
                          of Information and<br>
                          Communication, that this email is an advertisem=
ent and=20
                          the address of which<br>
                          has been gathered from bulletine boards on inte=
rnet=20
                          as well as that we do not<br>
                          have any further information about you other th=
an your=20
                          email address.<br>
                          If you don't want this type of information or e=
-mail,=20
                          please click<br>
                          the =A1=AE<a href=3D"http://www.redbrush.co.kr/=
email/reject.jsp?keyword=3Dcardcash&email=3Dtrigtran@ietf.org&type=3Dreje=
ct" OnMouseOver=3D"window.status=3D''" OnMouseOut=3D"window.status=3D''">=
E-mail=20
                          Reception Reject</a>' or the =A1=AE<a href=3D"m=
ailto:kdj5823@naver.com" class=3D"link">kdj5823@naver.com</a>'=20
                          and send me reply mail. </font></font><font siz=
e=3D"2"><br>
                          </font></div></td>
                    </tr>
                  </table>
                  <table width=3D"555" border=3D"0" cellspacing=3D"0" cel=
lpadding=3D"0">
                    <tr>=20
                      <td align=3D"center"><font size=3D"2">CopyRight =A8=
=CF 2003 www.card-cash.co.kr=20
                        All Right Reserved</font></td>
                    </tr>
                  </table> </td>
              </tr>
            </table> </TD>
        </TR>
      </TABLE></td>
  </tr>
</table>
</BODY>
</HTML>
_______________________________________________
Trigtran mailing list
Trigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/trigtran



From mailnull@www1.ietf.org  Mon Apr 28 07:24:50 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26826
	for <trigtran-archive@odin.ietf.org>; Mon, 28 Apr 2003 07:24:50 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3SBTMK32699
	for trigtran-archive@odin.ietf.org; Mon, 28 Apr 2003 07:29:22 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3SBTM832696
	for <trigtran-web-archive@optimus.ietf.org>; Mon, 28 Apr 2003 07:29:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26818
	for <trigtran-web-archive@ietf.org>; Mon, 28 Apr 2003 07:24:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19A6mI-0002Ap-00
	for trigtran-web-archive@ietf.org; Mon, 28 Apr 2003 07:26:34 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19A6mH-0002Al-00
	for trigtran-web-archive@ietf.org; Mon, 28 Apr 2003 07:26:33 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3SBTA832684;
	Mon, 28 Apr 2003 07:29:10 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3SBS4832652
	for <trigtran@optimus.ietf.org>; Mon, 28 Apr 2003 07:28:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26805
	for <trigtran@ietf.org>; Mon, 28 Apr 2003 07:23:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19A6l2-0002AP-00
	for trigtran@ietf.org; Mon, 28 Apr 2003 07:25:16 -0400
Received: from [218.144.69.102] (helo=firmsec.com)
	by ietf-mx with smtp (Exim 4.12)
	id 19A6kw-0002AG-00
	for trigtran@ietf.org; Mon, 28 Apr 2003 07:25:11 -0400
From: 알프레드<mailmaster@firmsec.com>
To: trigtran@ietf.org
Reply-To: mailmaster@firmsec.com
Mime-Version: 1.0
Content-Type: text/html; charset=ks_c_5601-1987
Message-Id: <E19A6kw-0002AG-00@ietf-mx>
Date: Mon, 28 Apr 2003 07:25:11 -0400
Subject: [Trigtran] (광고)불결해~!알프레드~~~~!!@
Sender: trigtran-admin@ietf.org
Errors-To: trigtran-admin@ietf.org
X-BeenThere: trigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=unsubscribe>
List-Id: Triggers for Transport <trigtran.ietf.org>
List-Post: <mailto:trigtran@ietf.org>
List-Help: <mailto:trigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>,
	<mailto:trigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h3SBTA832684
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

<div align =3D center><font size =3D 2>=C1=A4=BA=B8=C5=EB=BD=C5=BA=CE =B1=
=C7=B0=ED=BB=E7=C7=D7=BF=A1 =C0=C7=B0=C5 =C0=DB=BC=BA=C7=D1 <b>[=B1=A4=B0=
=ED]</b> =B8=DE=C0=CF=C0=D4=B4=CF=B4=D9.</font></div>
<div align =3D center><font size =3D 2>=B1=CD=C7=CF=C0=C7 e-mail =C1=D6=BC=
=D2=B4=C2 2003-04-12 =BF=C0=C8=C4 2:10:35 =BF=A1 <b>www1.ietf.org/mail-ar=
chive/working-groups/pilc/current/msg00233.html</b> =BF=A1=BC=AD =BC=F6=C1=
=FD=C7=DF=BD=C0=B4=CF=B4=D9.</font></div><hr size=3D1 noshade color=3D#CC=
CCCC style=3Dline-height:200%;><html>
<head>
<title>=C0=A5=B0=FC=B8=AE ALFRED</title>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Deuc-kr"=
>
</head>
<body>
<center><table width=3D"580" border=3D"0" cellspacing=3D"0" cellpadding=3D=
"0">
  <tr>=20
    <td align=3D"left"><a href=3D"http://www.firmsec.com" target=3D"_blan=
k"><img src=3D"http://firmsec.com/alfred/mail/logo.gif" border=3D"0"></a>=
</td>
    <td align=3D"right" valign=3D"bottom"><img src=3D"http://firmsec.com/=
alfred/mail/www.gif"></td>
  </tr>
</table>
<table width=3D"580" border=3D"1" cellpadding=3D"0" cellspacing=3D"0" bor=
dercolor=3D"#4a494a">
  <tr>
    <td><table width=3D"580" border=3D"0" cellspacing=3D"0" cellpadding=3D=
"0">
          <tr align=3D"right">=20
            <td height=3D"21" colspan=3D"2" background=3D"http://firmsec.=
com/alfred/mail/top_bg.gif"><img src=3D"http://firmsec.com/alfred/mail/to=
p_right_img.gif" width=3D"129" height=3D"25"></td>
          </tr>
          <tr>=20
            <td width=3D"444"> <img src=3D"http://firmsec.com/alfred/mail=
/main.gif" width=3D"433" height=3D"165"></td>
            <td width=3D"145" align=3D"middle"><a href=3D"http://www.firm=
sec.com/alfred/install.asp"><img src=3D"http://firmsec.com/alfred/mail/do=
wn.gif" width=3D"121" height=3D"165" border=3D"0"></a></td>
          </tr>
          <tr>=20
            <td height=3D"23" colspan=3D"2" background=3D"http://firmsec.=
com/alfred/mail/product_bg.gif">&nbsp;&nbsp;<img src=3D"http://firmsec.co=
m/alfred/mail/hexa.gif" width=3D"14" height=3D"14">=20
              <font color=3D"#003399" size=3D"2" face=3D"=B1=BC=B8=B2=C3=BC=
, =B1=BC=B8=B2, Verdana"><strong>=B3=BB=BF=EB=20
              =BC=B3=B8=ED</strong></font></td>
          </tr>
          <tr align=3D"middle">=20
            <td height=3D"642" colspan=3D"2"><img src=3D"http://www.firms=
ec.com/alfred/mail/main_text.gif" width=3D"580" height=3D"592"><br>=20
              <font color=3D"#ff0000" size=3D"2">=BE=CB=C7=C1=B7=B9=B5=E5=
 =BB=E7=BF=EB=BD=C3 =B9=AE=C0=C7=BB=E7=C7=D7=C0=BA <A href=3D"mailto:alfr=
ed@firmsec.com" >alfred@firmsec.com</a>=20
              =C0=B8=B7=CE =B9=AE=C0=C7=C7=CF=BD=C3=B1=E2 =B9=D9=B6=F8=B4=
=CF=B4=D9.</font><br> <br> </td>
          </tr>
		  <tr align=3D"middle" bgcolor=3D"#efefef">
            <td colspan=3D"2" background=3D"http://www.firmsec.com/alfred=
/mail/bottom_bg.gif"><font size=3D"2"> <br>
              <font color=3D"#0000ff"><A href=3D"mailto:spam@firmsec.com?=
subject=3D=BC=F6=BD=C5=B0=C5=BA=CE&amp;body=3D=BC=F6=BD=C5=C0=BB=B0=C5=BA=
=CE=C7=D5=B4=CF=B4=D9." ><u>=BC=F6=BD=C5=B0=C5=BA=CE</u></a></font> =B9=F6=
=C6=B0=C0=BB =C5=AC=B8=AF=C7=CF=BD=C3=B8=E9 =BC=F6=BD=C5=B0=C5=BA=CE=C3=B3=
=B8=AE=B0=A1 =C0=CC=B7=E7=BE=EE =C1=FD=B4=CF=B4=D9.<br>
              <br>
              If you don't want to receive this mail anymore, click here =
<A href=3D"mailto:spam@firmsec.com?subject=3DRejection&amp;body=3DRejecti=
on" ><u><font color=3D"#0000ff">[Deny]<br>
              <br>
              </font></u></a></font></td>
          </tr>
          <tr align=3D"middle"> </tr>
          <tr align=3D"middle">=20
            <td height=3D"75" colspan=3D"2"><img src=3D"http://www.firmse=
c.com/alfred/mail/bottom.gif" width=3D"580" height=3D"77"></td>
          </tr>
        </table></td>
  </tr>
</table>
</center>
</body>
</html>
_______________________________________________
Trigtran mailing list
Trigtran@ietf.org
https://www1.ietf.org/mailman/listinfo/trigtran



