Re: [swinog] ##### SwiNOG #32 - Agenda #####

2017-10-30 Diskussionsfäden Simon Ryf
Dear SwiNOGers

 

Final Agenda is online.

http://www.swinog.ch/meetings/swinog32/index.asp

 

(order can still change)

 

Please hurry up with your registration, we’ll close it this Friday 23:59.

After that, you’ll have to late reg with increased fee.

 

There are still slots for Speed Talks or a 30min talk. If you think you could 
last minute contribute, please let me know. Would be nice :-)

 

Tomorrow I will send you an update with a detailed Agenda including the 
abstracts.

 

Br

Simon

 

 

Important Dates for SwiNOG#31

03.11.2017 Registration closes (only late reg possible after that)

09.11.2017 Meeting day


___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog


Re: [swinog] background migration of swisscom connection from IPv4 native to v6 + DS-Lite

2017-10-30 Diskussionsfäden Scott Weeks



--- g...@space.net wrote:
From: Gert Doering 
To: Scott Weeks 
On Sun, Oct 29, 2017 at 02:53:41PM -0700, Scott Weeks wrote:

> I was not around for those discussions (and not being a computer 
> science person, nor wanting to go on this for too long as has been 
> endlessly done on other lists), but it seems TLV would have allowed
> 4 to be a subset of the new space.  I never heard that discussed 
> much and that's what I meant by my comment.

The point is: if you introduce a change to the packet format (and TLV
would be), you are no longer compatible with IPv4.  Which makes the
whole "I want this to be compatible so I do not have to change infra
or end points" totally moot.

Worse, then you have "old IPv4" and "new IPv4" machines who might or
might not be able to talk to each other, depending on which IPv4 address
the "new IPv4" got (a long one or a short one) - while with IPv6, you have
unmodified old IPv4 to ensure compatibility during the transition, and
then you turn it off (in 10 years or so).
---



I guess all ways IETF participants thought of a new 
address space would not have allowed backwards 
compatibility with IPv4?

Thanks for the explanation.  I appreciate it.  
Hopefully, others here find it interesting, too.

scott


___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog


[swinog] BlueWin and Cloudmark

2017-10-30 Diskussionsfäden DUCHET Rémy
Hello @ll,

 

We have some customers that have spam issues when sending email to
@bluewin.ch .

Since 2 months, all emails sent to @bluewin.ch recipients are marked junk.

 

That’s what we can trace :

 

X-Bluewin-Spam-Analysis: v=2.1 cv=eL3e9Cd1 c=1 sm=1 tr=0 p=fUeVjJJZ:8

a=qTcuhanu2jf2BI9KYv9RyA==:117 a=qTcuhanu2jf2BI9KYv9RyA==:17

a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=K_h_1cidfDUA:10

a=xqWC_Br6kY4A:10 a=02M-m0pO-4AA:10 a=oXc4haEe4je61EW4P-sA:9

a=wPNLvfGTeEIA:10 a=yMhMjlub:8 a=SSmOFEAC:8 a=VzdpOnGMIpnfysyMU8MA:9

a=rUqq3GAnYQ2zrqZp:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10

a=frz4AuCg-hUA:10 a=a4CKYyBK0OAZSS6edTcA:9 a=pA59YpQ9dOODYSR3:18

a=KQqxNPgzF0kA:10 a=359DcwL6FTx8MXQu2PII:22

X-Bluewin-Spam-Score: 100.00

 

If anybody from Bluewin can contact me off list

 

Thanks, 

Rémy



smime.p7s
Description: S/MIME cryptographic signature

___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog


Re: [swinog] background migration of swisscom connection from IPv4 native to v6 + DS-Lite

2017-10-30 Diskussionsfäden Gert Doering
Hi,

On Sun, Oct 29, 2017 at 02:53:41PM -0700, Scott Weeks wrote:
> I was not around for those discussions (and not being a computer 
> science person, nor wanting to go on this for too long as has been 
> endlessly done on other lists), but it seems TLV would have allowed
> 4 to be a subset of the new space.  I never heard that discussed 
> much and that's what I meant by my comment.

The point is: if you introduce a change to the packet format (and TLV
would be), you are no longer compatible with IPv4.  Which makes the
whole "I want this to be compatible so I do not have to change infra
or end points" totally moot.

Worse, then you have "old IPv4" and "new IPv4" machines who might or
might not be able to talk to each other, depending on which IPv4 address
the "new IPv4" got (a long one or a short one) - while with IPv6, you have
unmodified old IPv4 to ensure compatibility during the transition, and
then you turn it off (in 10 years or so).

Gert Doering
-- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AGVorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14  Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444   USt-IdNr.: DE813185279


___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog