Subject
From
Date
List
[Ltru] New 4646bis IANA registry published[Ltru] New 4646bis IANA registry published
Stephane Bortzmeyer
2009-07-30
ltru
/arch/msg/ltru/AO3Z-JlfDzrL7Jd-A79je_fB9AE/
877948
1468043
Re: [Ltru] New 4646bis IANA registry publishedRe: [Ltru] New 4646bis IANA registry published
Martin J. Dürst
2009-07-30
ltru
/arch/msg/ltru/fH7LNSQukfQwdJHEODPrsEgZNqY/
877949
1468043
Re: [Ltru] New 4646bis IANA registry publishedRe: [Ltru] New 4646bis IANA registry published
Stephane Bortzmeyer
2009-07-30
ltru
/arch/msg/ltru/9wBkBD_gmAsKdLzLkTtE3myfhYs/
877950
1468043
Re: [Ltru] New 4646bis IANA registry publishedRe: [Ltru] New 4646bis IANA registry published
Kent Karlsson
2009-07-30
ltru
/arch/msg/ltru/Bc7K6XzD-69N_tswN4huFjpMJbM/
877951
1468043
Re: [Ltru] New 4646bis IANA registry publishedRe: [Ltru] New 4646bis IANA registry published
Stephane Bortzmeyer
2009-07-30
ltru
/arch/msg/ltru/AkAYqaKipkm0aFRIJ0Rlo1eI3GA/
877952
1468043
Re: [Ltru] New 4646bis IANA registry publishedRe: [Ltru] New 4646bis IANA registry published
Stephane Bortzmeyer
2009-08-25
ltru
/arch/msg/ltru/Rt9qH-zlkNxI7RKGJbzd4vzEtsY/
877984
1468043
[Ltru] Ltru] RFC 3282: should we revise it?[Ltru] Ltru] RFC 3282: should we revise it?
CE Whitehead
2009-07-26
ltru
/arch/msg/ltru/K4nQfcPXe_8CbrB0JNyWt4MFAaY/
877943
1468044
[Ltru] RFC 3282: should we revise it?[Ltru] RFC 3282: should we revise it?
Phillips, Addison
2009-07-24
ltru
/arch/msg/ltru/rOwkhkoz4v0NNOmm1acefngOjXs/
877942
1468045
Re: [Ltru] RFC 3282: should we revise it?Re: [Ltru] RFC 3282: should we revise it?
Randy Presuhn
2009-08-05
ltru
/arch/msg/ltru/Q8AuO5b7wh58NxKvPsE2Mrk1Kd0/
877953
1468045
Re: [Ltru] RFC 3282: should we revise it?Re: [Ltru] RFC 3282: should we revise it?
Phillips, Addison
2009-08-05
ltru
/arch/msg/ltru/-H5jNQefog0MmTbsExqrals_Cew/
877954
1468045
Re: [Ltru] RFC 3282: should we revise it?Re: [Ltru] RFC 3282: should we revise it?
Doug Ewell
2009-08-06
ltru
/arch/msg/ltru/dd7ATh28erNYP6Awm9t-IGasDc8/
877955
1468045
Re: [Ltru] RFC 3282: should we revise it?Re: [Ltru] RFC 3282: should we revise it?
Phillips, Addison
2009-08-06
ltru
/arch/msg/ltru/apLb3MtJhOaQ3m3HrsmdynIuK9k/
877956
1468045
Re: [Ltru] RFC 3282: should we revise it?Re: [Ltru] RFC 3282: should we revise it?
Doug Ewell
2009-08-06
ltru
/arch/msg/ltru/gH2jWREXjKa_6IYpCMsL8-UG4Rc/
877957
1468045
Re: [Ltru] RFC 3282: should we revise it?Re: [Ltru] RFC 3282: should we revise it?
Martin J. Dürst
2009-08-22
ltru
/arch/msg/ltru/hUQVRoU5iFtYuU_zIrFuWPXnevA/
877982
1468045
Re: [Ltru] RFC 3282: should we revise it?Re: [Ltru] RFC 3282: should we revise it?
CE Whitehead
2009-08-06
ltru
/arch/msg/ltru/kfLxhF0zSHHy9VLbaNZ2GZAy7JE/
877965
1468045
Re: [Ltru] RFC 3282: should we revise it?Re: [Ltru] RFC 3282: should we revise it?
Harald Alvestrand
2009-08-19
ltru
/arch/msg/ltru/jaMaKBqU8Mc_XQaO87ADYqI6uj8/
877977
1468045
Re: [Ltru] RFC 3282: should we revise it?Re: [Ltru] RFC 3282: should we revise it?
John Cowan
2009-08-19
ltru
/arch/msg/ltru/AxvmtIWmLUIMnpaH7AqxXAbK1nw/
877980
1468045
[Ltru] Translation of RFC 4646bis[Ltru] Translation of RFC 4646bis
Felix Sasaki
2009-07-19
ltru
/arch/msg/ltru/9W3jpUE9OV5VmQ2uUagB-xppvRU/
877928
1468047
Re: [Ltru] Translation of RFC 4646bisRe: [Ltru] Translation of RFC 4646bis
Randy Presuhn
2009-07-19
ltru
/arch/msg/ltru/rkSB-B3LWPSgLJ28RHa3uPdN9os/
877935
1468047
Re: [Ltru] Translation of RFC 4646bisRe: [Ltru] Translation of RFC 4646bis
Felix Sasaki
2009-07-20
ltru
/arch/msg/ltru/YDJMe8M16q-aBW-jODwCG1xTsYA/
877936
1468047
Re: [Ltru] Translation of RFC 4646bisRe: [Ltru] Translation of RFC 4646bis
Stephane Bortzmeyer
2009-07-20
ltru
/arch/msg/ltru/LfSng0nRLqi8pP6RYfXnY6v750Y/
877937
1468047
Re: [Ltru] Translation of RFC 4646bisRe: [Ltru] Translation of RFC 4646bis
Felix Sasaki
2009-08-18
ltru
/arch/msg/ltru/OAvsvLHaOBhd3cSmUYKbhZTEALc/
877973
1468047
Re: [Ltru] Translation of RFC 4646bisRe: [Ltru] Translation of RFC 4646bis
Richard Ishida
2009-08-21
ltru
/arch/msg/ltru/LNvkN2v8bSgotpdmZQe3i9nnbQo/
877981
1468047
Re: [Ltru] Translation of RFC 4646bisRe: [Ltru] Translation of RFC 4646bis
Felix Sasaki
2009-08-22
ltru
/arch/msg/ltru/RrVH-2UcAIcecAI5OU4p3kHzvKk/
877983
1468047
Re: [Ltru] rechartering to handle 639-6 (was FW: Anomalyinupcomingregistry)Re: [Ltru] rechartering to handle 639-6 (was FW: Anomalyinupcomingregistry)
CE Whitehead
2009-07-16
ltru
/arch/msg/ltru/vAUsmRP1nxHvEPthvOZpAK8RjD8/
877918
1468046
Re: [Ltru] rechartering to handle 639-6 (was FW: Anomalyinupcomingregistry)Re: [Ltru] rechartering to handle 639-6 (was FW: Anomalyinupcomingregistry)
Peter Constable
2009-07-17
ltru
/arch/msg/ltru/L6LZKetDlJ_KYVw_iV6y2sQBNaQ/
877919
1468046
Re: [Ltru] rechartering to handle 639-6 (was FW: Anomalyinupcomingregistry)Re: [Ltru] rechartering to handle 639-6 (was FW: Anomalyinupcomingregistry)
CE Whitehead
2009-07-19
ltru
/arch/msg/ltru/L_gYL2mw_MDE6APYliDNyO6ZJMU/
877931
1468046
Re: [Ltru] rechartering to handle 639-6Re: [Ltru] rechartering to handle 639-6
Doug Ewell
2009-07-16
ltru
/arch/msg/ltru/3b3-Ay2eC84k54Q54vcgEqyLJMg/
877911
1468048
Re: [Ltru] rechartering to handle 639-6Re: [Ltru] rechartering to handle 639-6
Mark Davis ⌛
2009-07-16
ltru
/arch/msg/ltru/4AChfyrm6ScDi42J7xI-F92am0s/
877913
1468048
Re: [Ltru] rechartering to handle 639-6Re: [Ltru] rechartering to handle 639-6
John Cowan
2009-07-16
ltru
/arch/msg/ltru/ibziSUrt3Ke5y_LtNL0DIRmuJl4/
877914
1468048
Re: [Ltru] rechartering to handle 639-6Re: [Ltru] rechartering to handle 639-6
Phillips, Addison
2009-07-16
ltru
/arch/msg/ltru/vT8ZCi5Tkfg-SMIU8sm3jtFRM10/
877915
1468048
Re: [Ltru] rechartering to handle 639-6Re: [Ltru] rechartering to handle 639-6
Doug Ewell
2009-07-16
ltru
/arch/msg/ltru/Ll85XZUOsAHu9et8FjivYnVzx8Q/
877912
1468048
Re: [Ltru] rechartering to handle 639-6Re: [Ltru] rechartering to handle 639-6
Doug Ewell
2009-07-16
ltru
/arch/msg/ltru/-tG4bQBssrIzaVzFV2Ty1RvhHuU/
877916
1468048
Re: [Ltru] rechartering to handle 639-6 (was FW: Anomaly inupcomingregistry)Re: [Ltru] rechartering to handle 639-6 (was FW: Anomaly inupcomingregistry)
CE Whitehead
2009-07-15
ltru
/arch/msg/ltru/nrT2S0NsTQJm6FzSEc6tqWyQGmA/
877904
1468049
Re: [Ltru] rechartering to handle 639-6 (was FW: Anomaly inupcomingregistry)Re: [Ltru] rechartering to handle 639-6 (was FW: Anomaly inupcomingregistry)
Debbie Garside
2009-07-15
ltru
/arch/msg/ltru/SYbGQ49CkT37_auJ9ZhHjhW-nJk/
877905
1468049
[Ltru] rechartering to handle 639-6 (was FW: Anomaly in upcoming registry)[Ltru] rechartering to handle 639-6 (was FW: Anomaly in upcoming registry)
Phillips, Addison
2009-07-13
ltru
/arch/msg/ltru/K63E4FSrtqloHxRyEJDEZPxnpsk/
877873
1468050
Re: [Ltru] rechartering to handle 639-6 (was FW: Anomaly in upcoming registry)Re: [Ltru] rechartering to handle 639-6 (was FW: Anomaly in upcoming registry)
Peter Constable
2009-07-13
ltru
/arch/msg/ltru/BsQyUq0AJenlYqvv7HunMPda6AE/
877874
1468050
Re: [Ltru] rechartering to handle 639-6Re: [Ltru] rechartering to handle 639-6
Randy Presuhn
2009-07-13
ltru
/arch/msg/ltru/zI-4cgMgQruXZS3sibOvGnZoaoQ/
877875
1468050
Re: [Ltru] rechartering to handle 639-6Re: [Ltru] rechartering to handle 639-6
Mark Davis ⌛
2009-07-13
ltru
/arch/msg/ltru/73fqG-lpGrJG7a_HbRME_ECpnxQ/
877876
1468050
Re: [Ltru] rechartering to handle 639-6Re: [Ltru] rechartering to handle 639-6
Mark Davis ⌛
2009-07-13
ltru
/arch/msg/ltru/Htrif8tCj3v-MWs7Www-82yghNU/
877877
1468050